schlesimeister
Re:Claude Code Routines
on Friday April 17, 2026 @10:45AM (#47806515)
This is pretty close to what I've been working on. I'm building a CLI tool called fai that formalises a lot of what you're doing here — context lives in Markdown files in the project (we call it a vault), syncs with git, travels with the project across devices and tools. The session start/end review you're doing manually is baked into the workflow – fai captures decisions, patterns, and notes during a session and digests them at the end so the next session starts with a meaningful summary rather than a blank slate.
The independent journalling angle is interesting. We have a similar concept where the AI maintains its own notes separate from the shared project context. What you're calling Claudius's independent perspective, we'd call the session layer. Still in early release but the core mechanic is the same thing you've landed on... context that belongs to the project, not the platform.
Re:Claude Code Routines
on Wednesday April 15, 2026 @03:14PM (#47783827)
Software Stewarding
Re:Claude Code Routines
on Wednesday April 15, 2026 @03:05PM (#47783694)
I found your response interesting, I've been working on a tool that is trying to tackle the problem I think you're describing. It's a CLI tool that sits between you and whatever agent you're using — your context lives in plain Markdown files on your machine, git-backed, portable across Claude Code, Codex, Cursor, whatever. You own it. Switch between providers and it comes with you. Happy to share more, we're only starting to share it now. Here's our site: https://www.fathym.com/