chore: stop tracking local agent session state - #567
Merged
Conversation
The .codexclaw/ goalplans and ledgers are per-machine agent state. They were committed with 'git add -f' despite the ignore rule, and once tracked the rule stopped applying, so they rode along into main and preview. Untrack them (files stay on disk), drop two .DS_Store files that got in the same way, and add tests/repo-hygiene.test.ts so a forced add fails CI instead of landing silently. Also drop a registry.ts comment pointing at a .codexclaw evidence file that was never committed and cannot be resolved by any reader.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (7)
💤 Files with no reviewable changes (5)
📝 WalkthroughWalkthroughThe change removes two stored agent goal plans and their ledgers, broadens ChangesRepository hygiene
Provider metadata
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
lidge-jun
added a commit
that referenced
this pull request
Jul 27, 2026
The .codexclaw/ goalplans and ledgers are per-machine agent state. They were committed with 'git add -f' despite the ignore rule, and once tracked the rule stopped applying, so they rode along into main and preview. Untrack them (files stay on disk), drop two .DS_Store files that got in the same way, and add tests/repo-hygiene.test.ts so a forced add fails CI instead of landing silently. Also drop a registry.ts comment pointing at a .codexclaw evidence file that was never committed and cannot be resolved by any reader.
lidge-jun
added a commit
that referenced
this pull request
Jul 27, 2026
The .codexclaw/ goalplans and ledgers are per-machine agent state. They were committed with 'git add -f' despite the ignore rule, and once tracked the rule stopped applying, so they rode along into main and preview. Untrack them (files stay on disk), drop two .DS_Store files that got in the same way, and add tests/repo-hygiene.test.ts so a forced add fails CI instead of landing silently. Also drop a registry.ts comment pointing at a .codexclaw evidence file that was never committed and cannot be resolved by any reader.
lidge-jun
added a commit
that referenced
this pull request
Jul 27, 2026
It was committed despite the ignore rule and carries no content. Matches the same cleanup on dev/main/preview in #567.
This was referenced Jul 28, 2026
This was referenced Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
.gitignorehas listed.codexclaw/since the directory existed, but four fileswere tracked anyway on
dev,main, andpreview:These are per-machine agent state — goalplans and append-only ledgers describing
one operator's local work loop. They are not product code, they carry local
worktree paths and session ids, and no reader of this repository can act on them.
Why the ignore rule did not stop it
Two properties of git combine badly here:
git add -foverrides.gitignorewith no warning.later edit is staged like any normal file.
So a single forced add is permanent until someone explicitly untracks the path.
That is what happened, and the files then rode along into
mainandpreviewthrough ordinary promotion.
Changes
.codexclaw/files withgit rm --cached. Files stay ondisk; only the index entry goes away.
devlog/.DS_Storeanddevlog/_plan/.DS_Store, which reached the repothe same way (
.DS_Storeis also already ignored).tests/repo-hygiene.test.ts, which asserts againstgit ls-filesratherthan against
.gitignore. A forced add now fails CI on the commit thatintroduces it, instead of being discovered months later.
src/providers/registry.tsciting.codexclaw/evidence/260710_wp9_ollama_cloud_model_ids.md— that file wasnever committed, so the reference cannot be resolved by anyone. The adjacent
verification date is kept.
devlog/is deliberately left alone: unlike.codexclaw/, it is referenced fromsource comments across
src/and is part of how this project records designevidence.
Verification
bun test tests/repo-hygiene.test.ts→ 3 pass / 0 failfailed and reported the two tracked
.DS_Storefiles, which is how they werefound.
bun x tsc --noEmit→ passbun scripts/test.ts→ full suite pass, privacy scan passSummary by CodeRabbit
Bug Fixes
Tests
Maintenance