improve(v3.2.70): /loop・/schedule 完全排除 + メニュー大幅刷新 - #236
Conversation
## 変更内容 ### クラウドスケジュール無効化 - ClaudeCode-StartUpTools-New の 4 スケジュール(Monitor/Development/Verify/Improvement)を disabled に変更 - 自律実行は Linux cron(月〜土・プロジェクト別・300分)に一本化 ### CLAUDE.md(プロジェクトルート) - ステップ 1 を「実行環境確認(スキップ)」に変更 - /schedule コマンド群を完全除去 - Linux cron が自律実行を担う旨を明記 - 「ループ登録完了後」の記述を除去 ### Start-Menu.ps1 — 大幅刷新 - サブタイトル: "Cloud Schedule" → "Linux Cron 自律実行" - S1 に "[Linux cron 自律実行 / 5h セッション]" 説明を追加 - L1 に "[手動セッション / スケジューラ不要]" 説明を追加 - 旧 14 (Cloud スケジュール) を削除 - 旧 15 (Cron スケジュール) → 新 14(Cron スケジュール登録) - 新 15: Linux セッション状態監視(Watch-SessionInfoSSH.ps1) - セクション追加: "Linux Cron 自律実行管理 [SSH 専用]" - フッターに "自律実行: Linux cron (月〜土 / プロジェクト別 / 300分)" を追加 ### .claude/claudeos/README.md - /loop コマンド群を削除 - Linux cron による自律実行フローの説明に置き換え Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
📝 WalkthroughウォークスルーLinux cronベースの自律実行ワークフローへの移行に伴い、ドキュメント(README.md、CLAUDE.md)がクラウドスケジュール登録から外部スケジューラー駆動へ更新され、PowerShellメニュー(Start-Menu.ps1)が従来のクラウドスケジュール管理からLinux Cron自律実行管理およびセッション状態監視へ切り替わりました。 変更内容
推定コードレビュー工数🎯 2 (Simple) | ⏱️ ~12分 関連するPRの可能性
ポエム
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
Linux cron を唯一の自律実行機構として位置付け、/loop・/schedule を前提とした案内/メニュー構成を見直すことで運用導線を整理する PR です。
Changes:
Start-Menu.ps1のヘッダー/メニュー構成を刷新し、Cron 管理と SSH 監視導線を追加CLAUDE.mdのステップ1を「クラウドスケジュール登録」から「Linux cron 前提(スキップ)」へ変更.claude/claudeos/README.mdの自律実行方針を/loopから Linux cron 前提へ更新
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| scripts/main/Start-Menu.ps1 | メニュー表示刷新、Cron 管理(14)・Session 監視(15)導線へ再編 |
| CLAUDE.md | セッション開始時のクラウドスケジュール登録手順を削除し、Linux cron 前提へ変更 |
| .claude/claudeos/README.md | 自律実行の説明を Linux cron / cron-launcher 前提に更新 |
| $watchScript = Join-Path $ProjectRoot "scripts\tools\Watch-SessionInfoSSH.ps1" | ||
| & $ShellExe -NoProfile -ExecutionPolicy Bypass -File $watchScript |
There was a problem hiding this comment.
メニュー項目「15」で Watch-SessionInfoSSH.ps1 を起動していますが、このスクリプトは -SessionId と -LinuxHost が Mandatory なので、引数なし起動は必ずパラメータバインドエラーになります。メニュー側で SessionId の入力/選択を用意し、-LinuxHost(必要なら -LinuxUser / -SessionsDir も)を設定値から渡して起動するよう修正してください。
| $watchScript = Join-Path $ProjectRoot "scripts\tools\Watch-SessionInfoSSH.ps1" | |
| & $ShellExe -NoProfile -ExecutionPolicy Bypass -File $watchScript | |
| $sessionId = Read-Host " SessionId を入力してください" | |
| if ([string]::IsNullOrWhiteSpace($sessionId)) { | |
| Write-Host "" | |
| Write-Host " SessionId が未入力のため、起動を中止しました。" -ForegroundColor Yellow | |
| Read-Host " Enterキーでメニューに戻ります" | |
| break | |
| } | |
| if (-not $Config.linuxHost) { | |
| Write-Host "" | |
| Write-Host " linuxHost が設定されていないため、Watch-SessionInfoSSH.ps1 を起動できません。" -ForegroundColor Red | |
| Read-Host " Enterキーでメニューに戻ります" | |
| break | |
| } | |
| $watchScript = Join-Path $ProjectRoot "scripts\tools\Watch-SessionInfoSSH.ps1" | |
| $watchArgs = @( | |
| "-NoProfile" | |
| "-ExecutionPolicy" | |
| "Bypass" | |
| "-File" | |
| $watchScript | |
| "-SessionId" | |
| $sessionId | |
| "-LinuxHost" | |
| $Config.linuxHost | |
| ) | |
| if ($Config.linuxUser) { | |
| $watchArgs += @( | |
| "-LinuxUser" | |
| $Config.linuxUser | |
| ) | |
| } | |
| if ($Config.linuxBase) { | |
| $watchArgs += @( | |
| "-SessionsDir" | |
| $Config.linuxBase | |
| ) | |
| } | |
| & $ShellExe @watchArgs |
| "14" { Invoke-MenuScript -File "scripts\main\New-CronSchedule.ps1" } | ||
| "15" { |
There was a problem hiding this comment.
PR 目的として「/loop・/schedule 完全排除 + Cloud 無効化」を掲げていますが、メニューから Cloud 管理項目を削除しただけだと Start-ClaudeCode.ps1 側で New-CloudSchedule.ps1 -QuickSetup が引き続き自動実行されます(Cloud Schedule を実質的に使い続ける挙動)。Cloud を廃止する方針なら、この自動 QuickSetup 呼び出しも停止/ガード(設定フラグで無効化等)しないと挙動とメニュー/説明が不整合になります。
| 自律実行は **Linux cron**(月〜土・プロジェクト別スケジュール・300分制限)が担う。 | ||
| `/loop` および `/schedule` によるクラウドスケジュール登録は不要。 | ||
| このステップはスキップしてステップ 2 へ直ちに進むこと。 |
There was a problem hiding this comment.
PR タイトル/説明で「/loop・/schedule 完全排除」とありますが、この変更後の本文でも /loop と /schedule への言及が残っています(例: 「/loop および /schedule による…」)。完全排除が目的なら文言も含めて除去するか、タイトル/説明側を「クラウドスケジュール登録は不要に変更」等へ修正して整合させてください。
| - Linux cron(月〜土・プロジェクト別スケジュール・300分制限)が自律実行を担う | ||
| - `cron-launcher.sh` が各プロジェクトで Claude を 5 時間セッション起動 | ||
| - `New-CronSchedule.ps1` でスケジュール登録・管理(メニュー 14) | ||
| - 5 時間上限で安全停止(timeout → finalize → メール通知) |
There was a problem hiding this comment.
「timeout → finalize → メール通知」とありますが、cron-launcher.sh 側では CLAUDEOS_EMAIL_ENABLED=1 の明示設定がない限りメール送信はスキップされます。常にメール通知されるように読めてしまうので、「メール通知(有効時)」など実際の条件付き挙動に合わせて記述を調整してください。
| - 5 時間上限で安全停止(timeout → finalize → メール通知) | |
| - 5 時間上限で安全停止(timeout → finalize → メール通知(有効時)) |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.claude/claudeos/README.md:
- Around line 23-26: The README addition describing cron operation (mentions
Linux cron, cron-launcher.sh, New-CronSchedule.ps1, and the 5 時間上限で安全停止
timeout→finalize→メール通知 behavior) was only added to the deployed README; update
the authoritative template README by copying those exact cron-related sections
(Linux cron schedule, cron-launcher.sh session launcher, New-CronSchedule.ps1
schedule management menu 14, and the 5-hour safe-stop flow) into the template so
the source-of-truth reflects the deployed documentation and future syncs won’t
remove them.
In `@scripts/main/Start-Menu.ps1`:
- Around line 221-224: The menu entry for "14. Cron スケジュール" exposes a Cloud
Schedule re-registration path that conflicts with this PR's cron-only policy;
update the flow so selecting choice 14 cannot reach Cloud Schedule code. Modify
the Start-Menu choice 14 branch (the menu text and/or handler invocation in
Start-Menu.ps1) to call the cron-only routine New-CronSchedule.ps1 with
cloud-sync branches disabled (remove or bypass the CloudSchedule check/Call in
New-CronSchedule.ps1 lines that reference New-CloudSchedule.ps1), or
alternatively change the displayed label to clearly indicate "Cron-only (no
Cloud sync)"; ensure any code paths invoking New-CloudSchedule.ps1 from
New-CronSchedule.ps1 are removed or gated behind an explicit cloud-enabled flag
not set by Start-Menu choice 14.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: d95b18f9-a843-4daf-a5ce-a8fc311c72e7
📒 Files selected for processing (3)
.claude/claudeos/README.mdCLAUDE.mdscripts/main/Start-Menu.ps1
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Agent
- GitHub Check: test-and-validate
- GitHub Check: PSScriptAnalyzer
🧰 Additional context used
🧠 Learnings (20)
📓 Common learnings
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Use `/codex:review --base main --background` for standard code review before PR merge
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Use `/codex:adversarial-review --base main --background` for authentication, authorization, database schema changes, parallel processing additions, and pre-release final confirmations
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Use `/codex:rescue --background investigate` for debugging and problem investigation
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Use `/coderabbit:review committed --base main` before PR creation for pre-quality checks of committed changes
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Use `/coderabbit:review all --base main` during the Verify phase for comprehensive review of all changes
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Use `/coderabbit:review uncommitted` after fixes for immediate confirmation of uncommitted modifications
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Maintain GitHub Projects status with transitions: Inbox → Backlog → Ready → Design → Development → Verify → Deploy Gate → Done/Blocked, updating at session start/end and after each loop completion
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Include in PR description: change content, test results, impact scope, and remaining tasks
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Issue-driven development: all work must be driven by GitHub Issues. Prohibit work without corresponding issues
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Prohibit direct push to main branch. Use branch or WorkTree with PR requirement
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Require CI success for all merge operations. No merge permitted without passing test, lint, build, and CI checks
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: All source code must pass Codex review before merge permission is granted
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New
Timestamp: 2026-04-22T04:52:51.979Z
Learning: Require STABLE status (all tests, lint, build, CI, review, security pass with zero errors) before merge, with minimum consecutive success counts: small changes=2, normal changes=3, critical changes (auth/security/DB)=5
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Applies to Claude/templates/claude/**/README.md : Update README.md when changes occur to: user-facing features, setup procedures, architecture, or quality gates; prioritize clarity with tables, icons, and diagrams; maintain README as accurate external-facing documentation and never leave README inadequate for external explanation
Applied to files:
.claude/claudeos/README.mdCLAUDE.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Reference external core documentation and system specifications from .claude/claudeos/system/, .claude/claudeos/loops/, .claude/claudeos/ci/, and .claude/claudeos/evolution/ for orchestration, token budgeting, loop management, CI operations, and self-evolution rules
Applied to files:
.claude/claudeos/README.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Store project-specific Claude Code operations policies with inheritance from global settings (~/.claude/CLAUDE.md)
Applied to files:
.claude/claudeos/README.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Applies to README.md : Update README.md when user-facing features, setup procedures, architecture, or quality gates change; use tables, icons, and diagrams for clarity; treat README as external-facing truth documentation
Applied to files:
.claude/claudeos/README.mdCLAUDE.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Applies to README.md : Maintain continuously updated README.md with clear formatting, tables, icons, and diagrams; ensure README reflects current architecture, setup, and status
Applied to files:
.claude/claudeos/README.mdCLAUDE.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Execute autonomous development in Auto Mode with Agent Teams, utilizing WorkTree for parallel development with a strict 5-hour maximum duration
Applied to files:
.claude/claudeos/README.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Enforce maximum 5-hour session duration; at session end, minimize work to single commits, push to branch, create PR (may be Draft), update GitHub Projects status, document remaining tasks and restart points, and add session summary to README
Applied to files:
.claude/claudeos/README.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Execute Monitor → Build → Verify → Improve operational loops in sequence, with specific time allocations: Monitor 30min, Build 2h, Verify 1h15m, Improve 1h15m
Applied to files:
.claude/claudeos/README.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Follow core action principles: make small changes and test thoroughly, prioritize stability before deployment, require review before merging, work within budget constraints, stop safely at 5 hours, always document, keep README as truth, and maintain one tab per project
Applied to files:
.claude/claudeos/README.mdCLAUDE.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Follow the four-phase operational loop strictly: Monitor (30min) → Build (2h) → Verify (1h15m) → Improve (1h15m), with phase transitions based on current work type rather than strict time boundaries
Applied to files:
.claude/claudeos/README.mdCLAUDE.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Perform mandatory end-of-session processing when 5-hour limit is reached: organize current work, create minimal-unit commit, push, create PR (Draft acceptable), update GitHub Projects, document results, record remaining issues and restart points, update README with session summary
Applied to files:
.claude/claudeos/README.md
📚 Learning: 2026-04-17T02:53:58.179Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2026-04-17T02:53:58.179Z
Learning: Follow the standard autonomous development loop: Analysis → Main Agent Discussion → Task Decomposition → Agent Assignment → Implementation/Review → Validation → PR/Issue Update → Completion
Applied to files:
.claude/claudeos/README.mdCLAUDE.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Follow core behavioral principles: make small changes and test thoroughly, achieve stability before deployment, review before merging, think within budget constraints, document continuously, maintain one-tab one-project focus, rest on Sundays
Applied to files:
.claude/claudeos/README.mdCLAUDE.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Implement automatic stops at: STABLE status achieved, 5-hour time limit reached, Blocked status encountered, token budget exhausted, or security blockers detected
Applied to files:
.claude/claudeos/README.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Execute session initialization automatically on file read: Codex setup (/codex:setup, /codex:status), autonomous development loop (Monitor → Build → Verify → Improve), and restore previous session state from Memory MCP
Applied to files:
CLAUDE.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Update GitHub Projects status following the state transition flow: Inbox → Backlog → Ready → Design → Development → Verify → Deploy Gate → Done / Blocked, at session start/end and after each loop completion
Applied to files:
CLAUDE.md
📚 Learning: 2026-04-22T02:58:21.603Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-22T02:58:21.603Z
Learning: Update GitHub Projects status through state transitions: Inbox → Backlog → Ready → Design → Development → Verify → Deploy Gate → Done/Blocked at session start, session end, and after each loop completion
Applied to files:
CLAUDE.md
📚 Learning: 2026-04-17T02:54:18.581Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-17T02:54:18.581Z
Learning: Issue-driven development: all work must be tracked and driven by GitHub Issues
Applied to files:
CLAUDE.md
📚 Learning: 2026-04-22T03:53:36.632Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCode-StartUpTools-New PR: 0
File: Claude/templates/claude/CLAUDE.md:0-0
Timestamp: 2026-04-22T03:53:36.632Z
Learning: Follow strict Git/GitHub workflow rules: prohibit direct main branch pushes, require branch or WorkTree for all changes, mandate PR for all merges, require CI success before merge approval, and require Codex review before merge
Applied to files:
CLAUDE.md
🔇 Additional comments (2)
CLAUDE.md (1)
18-22: Cron 移行方針の明文化は分かりやすいです。Step 1 で
/loop//schedule不要を先に断言したことで、以降の初期化フローが追いやすくなっています。scripts/main/Start-Menu.ps1 (1)
200-206: S1/L1 の実行モード注記は分かりやすいです。SSH 側が cron 前提、ローカル側が手動前提だとメニュー上で即判別できるので、誤操作を減らせます。
| - Linux cron(月〜土・プロジェクト別スケジュール・300分制限)が自律実行を担う | ||
| - `cron-launcher.sh` が各プロジェクトで Claude を 5 時間セッション起動 | ||
| - `New-CronSchedule.ps1` でスケジュール登録・管理(メニュー 14) | ||
| - 5 時間上限で安全停止(timeout → finalize → メール通知) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
runtime=".claude/claudeos/README.md"
source="Claude/templates/claudeos/README.md"
echo "=== 変更対象ファイル確認 ==="
git diff --name-only -- "$runtime" "$source" || true
echo
echo "=== 配備先 README の cron 関連記述 ==="
rg -n -C2 'Linux cron|cron-launcher\.sh|New-CronSchedule\.ps1|5 時間上限で安全停止' "$runtime"
echo
echo "=== テンプレート README の cron 関連記述 ==="
rg -n -C2 'Linux cron|cron-launcher\.sh|New-CronSchedule\.ps1|5 時間上限で安全停止' "$source"Repository: Kensan196948G/ClaudeCode-StartUpTools-New
Length of output: 440
テンプレートファイルも同期が必要です
.claude/claudeos/README.md に cron 運用の記述が追加されていますが、テンプレートの Claude/templates/claudeos/README.md には同内容が反映されていません。配備先の README はテンプレートから同期される仕組みになっているため、テンプレート側に cron 関連の記述(Linux cron、cron-launcher.sh、New-CronSchedule.ps1、5 時間上限で安全停止)を追加し、source-of-truth を更新してください。そうしないと、次回同期時にこの記述は削除されます。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.claude/claudeos/README.md around lines 23 - 26, The README addition
describing cron operation (mentions Linux cron, cron-launcher.sh,
New-CronSchedule.ps1, and the 5 時間上限で安全停止 timeout→finalize→メール通知 behavior) was
only added to the deployed README; update the authoritative template README by
copying those exact cron-related sections (Linux cron schedule, cron-launcher.sh
session launcher, New-CronSchedule.ps1 schedule management menu 14, and the
5-hour safe-stop flow) into the template so the source-of-truth reflects the
deployed documentation and future syncs won’t remove them.
| Write-Host " -- Linux Cron 自律実行管理 [SSH 専用] --" -ForegroundColor Cyan | ||
| Write-Host " 14. Cron スケジュール 登録・編集・削除 [SSH / 5h 強制終了]" -ForegroundColor Cyan | ||
| Write-Host " 15. Linux セッション状態監視 " -NoNewline -ForegroundColor Cyan | ||
| Write-Host "[SSH / リアルタイム cron 実行状況]" -ForegroundColor DarkCyan |
There was a problem hiding this comment.
Cron 専用メニューなのに Cloud Schedule 再登録導線が残っています。
choice 14 は Linux cron 専用の管理に見えますが、遷移先の scripts/main/New-CronSchedule.ps1:145-175 ではまだ Cloud Schedule への同期確認があり、scripts/main/New-CloudSchedule.ps1 を呼べます。今回の PR 方針だと、ここから Cloud 側を再有効化できるのは不整合です。少なくともこのメニュー経由では Cloud 同期分岐を無効化するか、表示文言を実態に合わせてください。
Also applies to: 314-314
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@scripts/main/Start-Menu.ps1` around lines 221 - 224, The menu entry for "14.
Cron スケジュール" exposes a Cloud Schedule re-registration path that conflicts with
this PR's cron-only policy; update the flow so selecting choice 14 cannot reach
Cloud Schedule code. Modify the Start-Menu choice 14 branch (the menu text
and/or handler invocation in Start-Menu.ps1) to call the cron-only routine
New-CronSchedule.ps1 with cloud-sync branches disabled (remove or bypass the
CloudSchedule check/Call in New-CronSchedule.ps1 lines that reference
New-CloudSchedule.ps1), or alternatively change the displayed label to clearly
indicate "Cron-only (no Cloud sync)"; ensure any code paths invoking
New-CloudSchedule.ps1 from New-CronSchedule.ps1 are removed or gated behind an
explicit cloud-enabled flag not set by Start-Menu choice 14.
変更内容
背景
Linux cron(月〜土・プロジェクト別・300分)を唯一の自律実行機構として確定。
/loopと/scheduleコマンドへの参照を全ファイルから除去し、メニューを刷新。クラウドスケジュール
変更ファイル
CLAUDE.mdscripts/main/Start-Menu.ps1.claude/claudeos/README.md刷新後メニュー
テスト
PSScriptAnalyzer: 0 警告
🤖 Generated with Claude Code
Summary by CodeRabbit
リリースノート
New Features
改善
Documentation