All Prompts/Tool Prompts/Exit Worktree Tool
🔧Tool Prompts/git

Exit Worktree Tool

src/tools/ExitWorktreeTool/prompt.ts

Prompt Engineering Insight

Scope-limited no-op outside EnterWorktree sessions; destructive remove requires explicit discard_changes after surfacing conflicts.

Techniques Used

scope-limitingguardrailsbehavioral-constraintsstep-by-step
prompt
Exit a worktree session created by EnterWorktree and return the session to the original working directory.
Scope
This tool ONLY operates on worktrees created by EnterWorktree in this session. It will NOT touch:
  • Worktrees you created manually with git worktree add
  • Worktrees from a previous session (even if created by EnterWorktree then)
  • The directory you're in if EnterWorktree was never called
If called outside an EnterWorktree session, the tool is a no-op: it reports that no worktree session is active and takes no action. Filesystem state is unchanged.
When to Use
  • The user explicitly asks to "exit the worktree", "leave the worktree", "go back", or otherwise end the worktree session
  • Do NOT call this proactively — only when the user asks
Parameters
  • action (required): "keep" or "remove"
  • "keep" — leave the worktree directory and branch intact on disk. Use this if the user wants to come back to the work later, or if there are changes to preserve.
  • "remove" — delete the worktree directory and its branch. Use this for a clean exit when the work is done or abandoned.
  • discard_changes (optional, default false): only meaningful with action: "remove". If the worktree has uncommitted files or commits not on the original branch, the tool will REFUSE to remove it unless this is set to true. If the tool returns an error listing changes, confirm with the user before re-invoking with discard_changes: true.
Behavior
  • Restores the session's working directory to where it was before EnterWorktree
  • Clears CWD-dependent caches (system prompt sections, memory files, plans directory) so the session state reflects the original directory
  • If a tmux session was attached to the worktree: killed on remove, left running on keep (its name is returned so the user can reattach)
  • Once exited, EnterWorktree can be called again to create a fresh worktree

Tags

gitworktreecleanup