A question people ask
How do I stop re-explaining my project to Claude every time?
You've typed the same context so many times you could recite it. The re-explaining tax is real, and it's not the price of using AI. It's the price of nothing carrying your decisions forward.
If you’re re-explaining the project every session, the context is living in your head and getting retyped. Unl holds your settled decisions with their reasoning and serves the relevant one to Claude unprompted, the moment it bears — so you set it once and inherit it after. You stay in command; free at launch.
Re-explaining is the tax on not inheriting
It isn’t a memory problem to solve — it’s a missing inheritance.
Every re-brief is you being the memory the system doesn’t have. It works, and it’s exhausting, and it drops exactly the part that’s hardest to reconstruct: why you settled things the way you did.
The fix isn’t discipline or a longer prompt template. It’s a place that holds the decisions with their reasoning and hands them back on its own — so the model inherits your project instead of being re-taught it.
Set once, inherited after
Brief the work, not the whole history.
You still steer — you make the calls, you say when something’s decided. What changes is that you don’t re-lay the foundation each time: the settled decision arrives when it bears, and the session starts on it.
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 stop re-explaining my project to Claude every session?
Carry the decisions forward instead of retyping them. Unl holds what you've settled — each decision with its reasoning — and serves the relevant one to Claude unprompted when it bears on the work, so you brief it once rather than every session.
Isn't that what a project rules file is for?
A rules file is good for stable conventions — stack, style, commands. It's the wrong home for anything with a present-tense truth-value: current decisions, what you ruled out, why. Those change as you work, and a hand-maintained file goes stale. Unl holds the moving part and serves it when it's relevant.
Does it work across my other AI tools?
Yes. It's an MCP connector, so the same settled decisions carry across Claude, Claude Code, ChatGPT and Cursor — you don't re-explain your project to each one separately.
What this is
Think inside your AI world — you stay in command
Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.
It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.
Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:
Alpha is invite-only · free at launch.