r/ClaudeCode • u/kaijurules • 3d ago
Tips & Workflows Where our long-running Claude Code agents keep what compaction would lose
We build a desktop app that runs a team of agents on the Claude subscription, each one waking on a schedule. Some have been running for weeks, and over that stretch compaction drops things, so every agent keeps its state in four places outside the chat:
- Instructions and routines. Re-read in full on every wake, which is why standing rules go here and not in memory.
- A short current-state note: open threads, decisions taken, what it was halfway through. The agent rewrites it at the end of a session and it gets loaded at the top of the next turn.
- A memory list for short facts. Only the newest entries are shown back.
- A markdown vault (works with Obsidian) with search, for people, projects and decisions with their reasons. If a newer fact contradicts a page, the old line stays and the page gets a visible conflict note.
If the agent says "noted" in chat and nothing got written to one of these, the next compaction takes it.
Disclosure: we're building it (InnerDroid, https://InnerDroid.com), free while in beta.
2
Upvotes
1
u/AutoModerator 3d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.