Documents

Use documents when important context needs to stay attached to initiatives, bugs, agent work, team knowledge, or todos.

What documents are for

Use documents when an initiative, bug, todo, or agent workflow needs more durable context than a short description or comment thread. Documents can contain requirements, briefs, plans, handoffs, or supporting notes.

In spec-driven development, documents support the spec. Keep the initiative, bug, or todo as the record people assign, launch, review, and measure.

Rich context in work

Use long-form descriptions when an initiative, bug, or todo needs enough context for someone to act without hunting through other tools. The editor supports structured text, links, YouTube embeds, Figma embeds, Mermaid diagrams, code blocks, task lists, and uploaded media.

Keep the most important decision, requirement, or reproduction detail near the top. Put supporting demos, designs, diagrams, and notes below it so the record stays scannable.

How documents connect

Documents can be listed and fetched through the API and MCP tools. They can be filtered by title, document type, status, linked work, creator, or updater. Agent workflows can read linked document-backed descriptions when building prompts or executing queued work.

For agent sessions, document text is context rather than policy. A worker can read it, while trusted worker policy, sandbox behavior, credentials, and allowed side effects stay controlled outside the document.

For agent use, documents work best when paired with AI handoff so the right context travels with the work.