Run a workshop session
Workshops are AI-assisted conversations that produce your project documentation and the roadmap of versions the agent will build.
In the appWorkshops
Workshops are AI-assisted conversations that produce your project documentation and the roadmap of versions the agent will build.
A workshop is a conversation with the agent that turns an idea into two things: the documents that describe your product, and the roadmap: the list of versions the agent will build, one after another.
It is the normal way into a version. You talk, the agent writes, and what it produces is what gets built.
Create a session
The form never asks for a name. The agent names the session from your first exchange, when there is finally something to name. You can rename it later. See below.
The workspace
The workshop takes over the whole screen: no sidebar, its own topbar.
You talk on the left. What the session produces lands on the right.
A brand-new workshop opens full-chat: there is nothing to show on the right yet. The panel reveals itself the first time the agent produces something, and focuses whichever tab it landed in.
⌘B(Ctrl+B) toggles the panel by hand; the divider between the two can be dragged.Documents
The Documents tab groups everything the agent wrote by kind. Click any row to open it full-height.
Commenting is how you correct the specification. Select the passage that is wrong, say what you expected, and the agent rewrites that part, so you do not have to re-explain the whole document.
Roadmap
The Roadmap tab is the build pipeline: the versions the workshop created, in the order they will run, with the controls to launch them one by one or unattended. It has its own article. See Launch versions from the roadmap.
Rename
Click the workshop name in the topbar, then Rename. This is the only human path to a name, and it is one-way: once you have chosen one, the agent stops auto-naming that session.
Complete a session
Complete lives in the same identity popover, on the lifecycle row. It is locked until the workshop has produced a document or a version: the popover says so rather than hiding the control.
Completing releases the working environment and flips the conversation to read-only. It is not final: Reopen is in the same place, and the read-only composer offers it too. Reopening is cheap: the environment is rebuilt on your next message, with the artifacts restored.