269 — tp claude is removed (#269)
Why
tp claude runs claude --dangerously-skip-permissions after checking
that it is in a git worktree whose .claude/settings.json turns the
sandbox on. It belongs to the flow before the ladder, where a human
opened a tp wt worktree in an editor and started an agent in its
terminal. At code level 3 agents are started by the session that runs
the flow, in worktrees it makes for them, and none goes through
tp claude. What is left is a command whose only act is to turn the
permission prompts off, kept in a tool that otherwise has no say in how
an agent is run.
What changes
tp claude: removed, at every code level. It is an unknown command, as any other name is.internal/claude: the package goes with it.README.md(thetp claudesection),docs/worktrees.md(Quick Start, Typical Workflow, the Commands row and "TheclaudeCommand") andCLAUDE.md(Key commands): the command is no longer named.
Acceptance
| Command | Outcome |
|---|---|
tp claude, with or without arguments, in a worktree or not |
the unknown-command error; claude is not started |
tp -a and the command list |
no claude row |
tp wt agent NAME --spec=… |
as today: it runs claude itself and never went through tp claude |
tp wt start at levels 0 and 1; tp idea story at level 3 |
the sandbox .claude/settings.json is written, as today |
| Searched | Outcome |
|---|---|
README.md, docs/worktrees.md, CLAUDE.md, the usage text |
no mention of tp claude or task-plus claude |
| the Go packages | no internal/claude |
Out of scope
- The sandbox
.claude/settings.jsona worktree is given: it guards aclaudestarted by hand as much as one started bytp claude. tp wt agentand the dashboard.- A deprecation period or a message naming what to run in its place:
claudeis run directly. - Mentions in
CHANGELOG.mdand in earlier stories, which record what was.
Decisions
None.
Done when
- tests express the acceptance table and pass
- spec updated
- changelog entry
- issue closed with a link to the release