Skip to content

chore: ignore the per-machine Claude Code state, not the reviewable half - #21

Merged
P0w3r223 merged 1 commit into
mainfrom
chore/ignore-local-claude-state
Sep 9, 2026
Merged

P0w3r223 merged 1 commit into
mainfrom
chore/ignore-local-claude-state

Conversation

@P0w3r223

@P0w3r223 P0w3r223 commented Sep 9, 2026

Copy link
Copy Markdown
Owner

What

Ignore .claude/sessions/, .claude/settings.local.json and .claude/worktrees/.

Why

These are per-machine: a session handoff, one machine's permission grant, and — where present —
throwaway checkouts of this repository that a subagent runs in.

Left untracked and unignored, the first permission grant on any other checkout makes
git status report a change that is not one. That is a standing false finding in an
instrument whose whole value is that a finding means something, and it is currently
reproducing: this repository reads dirty to git status while its working tree is in fact
clean.

Why not .claude/ wholesale

.claude/settings.json is reviewable configuration — a hook nobody can read is a hook nobody
can correct — so it stays trackable if this repository ever adds one. Only the paths that can
never be reviewed are ignored.

These paths are per-machine: a session handoff, one machine's permission grant, and where
present the throwaway checkouts a subagent runs in. Untracked and unignored, the first
permission grant on any other checkout makes `git status` report a change that is not one — a
standing false finding in an instrument whose whole value is that a finding means something.

Scoped rather than blanket: `.claude/settings.json` is reviewable configuration and stays
trackable if this repository ever adds one.
@P0w3r223
P0w3r223 merged commit 9864e73 into main Sep 9, 2026
2 checks passed
@P0w3r223
P0w3r223 deleted the chore/ignore-local-claude-state branch September 9, 2026 11:25
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