Plans feel very different depending on the provider. Codex usually keeps a
checklist for the current turn. Claude can remember rich tasks for weeks. T3 Tasks
could give every thread the same durable task memory, with stable IDs that survive
compaction.
/taskSave it without interrupting the agent
#245Still useful weeks and compactions later
any providerSame behavior on Codex, Claude, and the rest
Plans say what the agent is doing now. Tasks remember what the
thread needs to come back to.
Inspired by a two-month Claude Code session where numbered tasks stayed
useful through weeks of work and repeated context compaction. That behavior is worth having
on every provider.
Today it depends on the provider
T3's experience is otherwise unified. Task memory is where it splits:
Codex & most providersA turn-scoped plan. Useful while the agent works, but not a backlog you can
return to next week.
Claude CodeRich, numbered tasks that stay useful through compaction and weeks of work.
This is the bit worth making consistent.
One durable task list, owned by T3
Each thread gets a small task list above the composer. No sidebar and
no new page. Shared T3 tools let every provider read and write the same list, while provider
plans stay in the timeline where they already belong.
Tap the mockup to open it full size
Stable IDs you can say out loud. “What was #245?” works weeks later, after any number of compactions.
Task ≠ plan, visibly. The plan checklist stays in the turn where it belongs; tasks persist above the composer.
Nothing new to learn per provider. The same panel, tools and behavior everywhere T3 runs.
Two ways to save the thought
Both paths store the exact words immediately with a stable ID.
Out-of-band captures can be enriched in the background. Conversational captures get the
benefit of the active agent's context.
/taskSave it out of band. The running agent never sees it.
“Log that as a task”Use the active agent's working understanding of what “that” means.
Saved immediately
Task created#245“Log the focus-ring bug — happens after closing the command palette with Escape”saved · writing brief…
Enriched in the background
Task created#245Focus ring lost after closing command palette with EscCurrent: Open
Weeks later
Task created#245Focus ring lost after closing command palette with EscCurrent: Done ✓
You choose the path. T3 never guesses or silently reroutes composer text.
Saved first, enriched second. The task never depends on generation succeeding.
Still there when you come back
Ask “what's still outstanding?” or open #245
directly. The answer comes from the task record, not from whatever survived conversation
compaction. Any provider running the thread can retrieve, update and complete it.
Tap the mockup to open it full size
Open / Done, reversible. Completion is one step, and reopening loses nothing.
The chip stays where the thought happened. It keeps the original context while always showing the current status.
Deliberately not a task tracker. No cross-thread ledger, board, attempts,
sprints or assignees. Provider plans are left exactly as they are. If thread task memory proves
useful, moving tasks between threads can come later.
