I’d love to know everyone’s approach to this - I’ve seen so much going on online but none of it really aligns with the way I operate across multiple projects and need context that’s specific to each one, with the ability to update it as things change. I ended up building my own thing around this - it’s called ALIVE and it’s basically a file- based context layer that sits on top of Claude Code. each project gets its own context unit with a set of markdown files that track current state, decisions, tasks, people, domain knowledge etc etc. then there’s a broader system layer that manages your world across all of them - who’s involved, what’s active, what needs attention, that sort of thing. It is tied together with a bunch of hooks and skills that ensure that each agent has relevant information at the start and then stores the relevant information at the end too. It is open sourced on gh at https://github.com/alivecomputer/alive-claude if anyone wants to sus it out I have been using it pretty heavily across around 60 sessions now and it’s kind of changed the way I work - sessions pick up where they left off, decisions don’t get lost, and I’m not spending 20 minutes re-explaining everything each time. but I’m also still iterating on it and looking for ways to improve so keen to hear what’s working for other people too. Happy to help anyone out who wants to have a go at setting something like this up or just wants to chat about the approach - always keen to compare notes on this stuff. submitted by /u/bananabooth
Originally posted by u/bananabooth on r/ClaudeCode