cli: worktree status and rebase exist only on the MCP surface - bring them to the CLI or pin them agent-only #170
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#170
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
madt_worktreesdispatches list / status / add / remove / rebase / prune. The CLImadtea worktreesupports only list / add / remove / prune. The two missing ones are not niche:statusis the batch clean/dirty/ahead-behind report across every tree, andrebaseis the guarded re-base of a worktree's branch (refuses primary checkouts) - both useful to a human running a multi-worktree setup, not just to agents.Decide one:
worktree statusandworktree rebaseto the CLI. Natural fit with the cobra-subcommand conversion in #169; the names already match the MCP actions, so parity is free. COMPARISON.md rows follow.Context: the README taught
worktree statusandworktree rebaseas CLI commands until 2026-07-16 (fixed in the readme-edits batch, which now attributes them to MCP). #169 covers the drift-test hole that let that ship.Parity is ideal, going to bring them in.