I never worry about starting a new session, we work, I `/clear` and then `run boot up ref:resume`
Every project is the same
I can run multiple projects this way
We start right back up where we left off
Mandrel
This happens every time a new model is getting ready to come out. It's a pattern. I don't see this with my work but I can always count on X to inform me a new model is imminet.
My uneducated guess is they have to change the harness and tune it. Which changes how current model performs.
I also think this is severely over blown.
How to have a full-time job and still get work done.
Mandrel Punch Loop:
Scope the work->file punches with required 'proof'->Picker selects based on dependency order->Foreman builds->Critic inspects->Merge on pass or send back to be re-selected
Mandrel OSS - making good progress. Just a few more things and I will put Mandrel up against any other AI project management/memory tool.
My portfolio so far.
Mandrel
Backstory (Omarchy)
Omarcade (Omarchy)
Wobble Party (Omarchy)
Custom Runtime
Not done yet!
This is another example of how project memory/management can help. You can split sessions (orbs) from context handoffs. More importantly you can save the ‘why’.
If your concern is stale context, Mandrel goes to great lengths to remove conflicts and marks superseded context as such.
Give your Omarchy agents (Claude, Codex, PI, Hermes) a working memory. Start your agents from your last work with boot hook and handoffs. Switch agents and memory goes with it.
Backstory
Introducing Backstory for @OmarchyLinux
I have used a heavier version of this for over a year now and wanted to bring memory to your Omarchy projects.
I need a few people to test this for me before I submit to Marketplace as plugin. If you are interested reach out!



















