A question people ask
How do I keep Claude on track across sessions?
Every new session, Claude is sharp — and starting from nothing. Staying on track shouldn't mean re-briefing it each time. It should mean the model inherits what you already decided.
The fix for drift across sessions isn’t a longer prompt each time — it’s inheritance. Unl holds your settled decisions with their reasoning and serves the one that bears on the current step, unprompted, so Claude picks up on your rails instead of its own defaults. You stay in command; it’s free at launch.
Repetition is a symptom, not the fix
It isn’t a memory problem to solve — it’s a missing inheritance.
If keeping Claude on track means re-explaining the project every session, the track isn’t being carried anywhere — it’s being rebuilt from memory, yours, each time. That’s the tax.
The track is your decisions: what you’re aiming at, what you’ve settled, what you ruled out. When those inherit — arrive in the model’s context the moment they bear — the session starts where the last one finished.
Aimed, not just remembered
A committed target is the fixed point the work compounds toward.
Beyond single decisions, Unl carries a target: the thing you set out to do. Held across sessions, it’s the point the work moves toward instead of drifting toward whatever comes next — momentum, not just recall.
How it works
Connect once. From then on, what you settled arrives on its own.
1 · Connect. Add the MCP connector in a couple of steps, about five minutes. It plugs into Claude, Claude Code, ChatGPT & Cursor as an MCP connector.
2 · Settle a decision. When you make a call, it’s held with its reasoning — on your word, never scraped. Change your mind and it’s superseded, the old one retired.
3 · It arrives unprompted. Next session, the decision that bears on the work is served into the model’s context the moment it’s relevant — you don’t fetch it, and you don’t re-explain it. The model inherits what you decided and builds from it.
Questions people ask
How do I keep Claude on track across multiple sessions?
Carry your decisions forward instead of re-briefing. Unl holds what you've settled — each decision with its reasoning, plus the target you're working toward — and serves the relevant one unprompted when it bears on the step, so each session builds from where the last ended.
Why does Claude drift off track when the conversation gets long?
A long session dilutes the early context, and a new session has none of it. Neither is fixed by repeating yourself. Inheriting the settled decision — served at the moment it's relevant — keeps the model on your rails without you holding the whole thread in your head.
Does this work outside Claude?
Yes — one set of settled decisions, carried over MCP across Claude, Claude Code, ChatGPT and Cursor. The same track meets you wherever you work.
What this is
Think inside your AI world — you stay in command
Save the thoughts, decisions and targets worth keeping, each with its reasoning, carried into every AI session the moment they matter. A new unit of exchange between you and your AI: the Settled Why with standing that travels. Unprompted.
Your whole AI world. What you decided at the epicentre. It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector — quick to connect, in a couple of steps.
MCP native·Human settled·Model agnostic·Your data
Reflections
Connect Unl to keep useful thoughts with their why.
Kept with its reasoning, without becoming a rule unless you settle it.
The full product, open. Free at launch.