Never lose the work you discover along the way.

One place for work that matters — but not right now

During a long agent session, real work constantly appears outside the current scope: a bug, a missing test, an edge case, a decision for later. A task saves that intent without turning it into a new thread or a heavyweight team ticket.

tap image for the full ledger

• A stable ledger, not another attention inbox. No unread counts; agents working elsewhere never reorder it.
• The user's original words remain immutable. The capture sentence is the record's spine.
• Generated context is labelled. Inference never masquerades as fact — files carry their basis.
• A task can wait for weeks without becoming stale, urgent, or guilt-inducing.

Two ways to save the thought

Either way, T3 stores the exact words immediately. Out-of-band captures can be enriched in the background; conversational captures benefit from the active agent's working 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.

• You choose the path. T3 never guesses or silently reroutes composer text.
• Saved first, enriched second. The task never depends on generation succeeding.
• The chip is anchored where the thought happened — permanent provenance, always showing the task's current status.

Come back when you're ready

Ask “what's still outstanding?” or open #245 directly — the answer comes from the durable task record, not from whatever survived conversation compaction. When you decide to act, start a focused thread with any provider: the original capture, brief, and provenance come with it.

• Readable without archaeology. Original words, provenance, and a labelled brief — enough to act on months later.
• “Open at origin” jumps to the exact turn where the task was born.
• Logged with Claude, started with Codex — or any other provider. The choice happens when you act, not when you capture.

Intent stays separate from execution

Tasks record what remains to be done. Threads record conversations. Attempts record bounded episodes of work. A failed run leaves the task Open; finishing an attempt does not silently close the task.

# Task

Durable intent. Original capture, brief, provenance, lifecycle: Open · Done.

has zero or more ↓

Attempt

One bounded episode of work — provider, model, outcome, evidence.

recorded in ↓

Thread

The conversation. Its plan checklist belongs to the turn, never to the task.

Close with confidence. Reopen without archaeology.

An agent can propose completion; the task stays Open until you close it. Reopening preserves the original finding, every attempt, and why the previous fix wasn't enough.

• Evidence rides with the task forever — tests, screenshot, diff. “Did we actually fix this?” has an answer.
• The next agent sees the whole story: the original finding, the first fix, and the Safari counter-example.

Capture it from your pocket

The thought most likely to be lost is the one you have away from your desk. Shipped V1 includes offline-safe mobile capture, a compact project list, readable task detail, and #245 deep links.

A ledger, not a project manager. No sprints, story points, assignees, due dates, or required tags. When a private working note becomes team work, it should be easy to promote it to GitHub or Linear later — without losing the original task context.

• sprints
• story points
• assignees
• due dates
• required tags
• boards
• capacity planning

The smallest version worth validating