Use case

Keep a multi-week project anchored, not adrift.

A big effort spans dozens of sessions over weeks. The agent writes a tidy plan on day one — and by day three it's fiction. Step two turned out wrong, step four got skipped, step five is marked "done" with nothing to show for it. The checklist still looks authoritative; it just no longer describes reality. That's plan rot, and it's the default state of every markdown to-do list an agent has ever written.

CTXone makes the plan a first-class object in the graph — one that survives the session and demands evidence — so a project that takes a month doesn't lose the thread on day three.

Plans that survive the session

# Stand up a plan the whole project shares
ctx plan new "auth refactor"
ctx plan add "extract token validation into middleware"
ctx plan add "migrate sessions table"

# Weeks later, in a brand-new session:
ctx plan next
    → next: extract token validation into middleware

# Done means proven, not just checked
ctx plan done 1 --proof commit:abc1234

That --proof flag is the point. A task isn't done because someone typed an x — it's done because it's anchored to a commit, a test run, or an artifact you can go look at. The plan and the work stay married for the life of the project.

What changes

  • No more restarting cold. Open a new session after a week off, ask ctx plan next, and pick up exactly where the project left off.
  • Progress is provable. Every completed task carries proof, so "how far along are we?" has a real answer, not a vibe.
  • Plans branch with context. Sandbox a speculative direction on a branch — plan and memory together — then diff and merge it when it holds up.
  • Shared on a team hub. On CTXone Team, the plan lives on the shared hub, so work-in-flight is visible to everyone instead of trapped in one person's chat history.

Who it's for

Anyone driving a long refactor, migration, or build-out with an AI agent across many sessions — where the cost isn't a single wrong answer, but slowly losing track of where the whole effort stands.

Next: The cure for plan rot  ·  Features & commands  ·  All use cases