Make sure StrawPot opt out Claude Code Schedule tool when spawning claude code.

[juhgiyo]

Make sure StrawPot opt out Claude Code Schedule tool when spawning claude code.

The agent keep scheduling with claude code internal schedule instead of StrawPot Schedule.

We need to opt out claude code schedule when starting claude code cli.

[juhgiyo]

Triage Summary

Type: Bug
Priority: p1-high

Rationale

Bug classification: When StrawPot spawns Claude Code via the wrapper (claude_code/wrapper/main.go), Claude Code's built-in scheduling tools (e.g., CronCreate, CronDelete, CronList) remain available to the agent. This causes agents to schedule tasks through Claude Code's internal scheduler instead of StrawPot's orchestrator-managed scheduling — meaning scheduled work becomes untracked by the StrawPot system.

p1-high priority: This is a significant behavioral issue that undermines StrawPot's orchestration model. The whole point of StrawPot scheduling (via denden) is centralized visibility and coordination. Agents silently using Claude Code's native scheduler bypasses this, creating ghost schedules that the orchestrator can't see or manage. There's no workaround short of manually instructing every role prompt to avoid Claude Code scheduling, which is fragile.

Suggested Fix Direction

The Claude Code CLI supports --disallowedTools flag to opt out specific tools. The wrapper in main.go → cmdBuild() should append something like:

--disallowedTools CronCreate,CronDelete,CronList

This would prevent agents from accessing Claude Code's native scheduling while preserving all other tool access.

[juhgiyo]

🔄 Pipeline: Triaged by automation. Categorized as bug / p1-high.

• Add pipeline/approved label to advance to planning.
• Add pipeline/blocked to hold.

[juhgiyo]

🔄 Pipeline: Approved for planning (fast-tracked by orchestrator on user request).

[juhgiyo]

🔄 Pipeline: Planning started. Decomposing into sub-issues...

[juhgiyo]

Implementation Plan

Scope: Block Claude Code's built-in scheduling tools (CronCreate, CronDelete, CronList) in the Go wrapper so agents always use StrawPot's orchestrator-managed scheduling.

Sub-issues: 1 task, estimated size/S total effort (~30 min)

Approach: This is a surgical, single-location fix. The cmdBuild() function in main.go builds the Claude CLI command array — we add one unconditional --disallowedTools flag. No decomposition needed beyond one sub-issue because the change is 2 lines of production code + 1 test function.

Execution Order

1. 1/1: Add --disallowedTools flag to cmdBuild() to block Claude Code scheduling #21 — Add --disallowedTools flag to cmdBuild() to block Claude Code scheduling (size/S)

Key Decisions

• Unconditional, not configurable. There is no valid use case for StrawPot agents to use Claude Code's native scheduling — StrawPot's orchestrator (denden) must see all scheduled work. Making this configurable would add complexity with no benefit and risk the same bug reappearing through misconfiguration.
• Single sub-issue, not forced decomposition. The fix is 2 lines of Go + 1 test function in 2 files. Splitting this further would be over-engineering.
• Placed after --dangerously-skip-permissions block. This keeps tool restriction flags grouped together in the command construction logic.

Dependencies & Risks

• Low risk. The --disallowedTools flag is a documented Claude Code CLI feature. The wrapper already uses similar flags (--permission-mode, --dangerously-skip-permissions).
• No external dependencies. Zero third-party packages involved.

Out of Scope

• Making the disallowed tools list configurable via --config JSON (not needed — see key decisions above)
• Blocking other Claude Code built-in tools beyond scheduling
• Changes to the StrawPot denden skill or orchestrator