Skip to content

chore: ignore .claude/worktrees agent dispatch residue#94

Open
Goosterhof wants to merge 1 commit into
mainfrom
chore/ignore-claude-worktrees
Open

chore: ignore .claude/worktrees agent dispatch residue#94
Goosterhof wants to merge 1 commit into
mainfrom
chore/ignore-claude-worktrees

Conversation

@Goosterhof
Copy link
Copy Markdown
Contributor

Summary

Adds .claude/worktrees/ to .gitignore to stop agent-dispatch worktree directories from surfacing as untracked content in git status. Four stale agent worktrees (agent-a549..., agent-a5e3..., agent-acdd..., agent-ade6...) from May 8 + May 15 dispatches were also removed from disk.

Why

When a war-room agent (spy or soldier) is dispatched with isolation: "worktree", the Claude Code harness creates a worktree at .claude/worktrees/agent-{id}/. These accumulate over time and clutter git status on every workstation that's run dispatches. The directory is ephemeral session state and should never be tracked.

Scoped narrowly to .claude/worktrees/ rather than the whole .claude/ directory — leaves room for tracked agent config (settings.json, agents, skills) later if fs-packages decides to ship one.

Test plan

  • git status clean on a fresh clone with no dispatches run
  • After running an agent with worktree isolation in this repo, .claude/worktrees/agent-*/ does not appear as untracked

🤖 Generated with Claude Code

@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying fs-packages with  Cloudflare Pages  Cloudflare Pages

Latest commit: 1c7a981
Status: ✅  Deploy successful!
Preview URL: https://cfcb7659.fs-packages.pages.dev
Branch Preview URL: https://chore-ignore-claude-worktree.fs-packages.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant