One thread per change.
Eight surfaces, one URL.
Every product change opens a thread. The brief, chat, document, whiteboard, agent runs, dev workspace, live preview, file diffs, and GitHub PR live at the same address. The team works there. The agent works there. The record stays there.
Everything that defines a change, in one place.
Surfaces aren't tabs you switch between. They're views of the same shared context. Edit any one, and the rest stay current.
The why
Goal, acceptance criteria, owner. Authored by the team. Read by humans and the agent on every run.
The conversation
Markdown chat with threading and presence. Mention @agent to call it. Replies stay attached to the work.
The document
Real-time collaborative document. Specs, decisions, and notes that everyone can edit at the same time.
The Excalidraw surface
Sketch, sticky, lasso. Hand a region of the board to the agent and it reads the shapes as instructions.
The dev environment
An isolated Kubernetes pod, scheduled in your own cluster, with your repo cloned, dependencies installed, and a real terminal. Spins up in under two seconds.
The live URL
Every thread gets a stable, named preview address. Reviewers click, comment, and the agent re-runs against the same URL.
The file changes
Inline diffs for every file the agent touches. Comment on a line. The agent picks the comment up on its next run.
The merge
One GitHub PR per thread, kept in sync. Reviewers see the diff, the brief, and the discussion side by side.
The agent is one of the people in the room.
Most AI coding tools start with one engineer and a private session. Threaded starts with the team. The PM writes the brief in the same thread the engineer reviews the diff in, where the designer dropped the Figma export.
The agent reads the whole thread on every run, not just the prompt that called it. Decisions made in chat are inputs to the next agent run. Comments left on a preview become the next set of changes.
When you come back to the thread Monday morning, you don't reconstruct context. The thread already kept it for you.
From idea to merge, in one URL.
- Open a thread for each product change.Anyone on the team can. Threads are scoped to one feature, one fix, one experiment.
- Write the brief together.Goal, acceptance criteria, owner. Two minutes. The agent reads it on every run.
- Sketch, chat, decide.Use the whiteboard, the doc, or chat. Decisions accumulate into a single Outcome Package the agent can act on.
- Hand the package to the agent.It runs in your dev workspace, ships changes, and posts a preview URL.
- Review in place.Click on the preview. Comment on a line. The agent picks up your comments and runs again.
- Merge.The thread closes with a connected GitHub PR. The history stays linked.
Ship your first thread.
Threaded is rolling out to teams of five to fifty. Invite-only while we tune the agent for production repos.
Request access →