Design through conversation
On desktop, open Staves from a board. Start with an example, a question, or the change you want to explore. You can design new work before there is a repository, or remodel a workflow that already exists.
Scope and intention
Section titled “Scope and intention”Selecting something on the canvas does not silently switch the conversation. Use the scope bar at the top of the panel — it names the scope and offers Back to whole workflow.
The working intention records what you want to work on in this conversation. It saves with the board and is separate from the workflow goal, accepted design and implementation status. The board conversation and each job conversation have their own intention and transcript.
Unsent drafts and your last selected scope stay in this browser. Reopening restores them. Return context shows recorded conversation turns and questions; when the saved design differs from the previous visit, it flags that earlier replies may refer to an older design.
Build and review
Section titled “Build and review”Eligible graph changes apply automatically by default, in batches that can be undone. Changes requiring human review still remain proposals. Auto-update, below the message box, is the preference that controls this. Switching the conversational activity does not change it.
Close the panel whenever you want; your conversation stays. Stop interrupts an in-flight response. Scenario checks are a separate action — Check a scenario in the + menu beside the message box — and alternatives are under Board options on the board. Neither is a mandatory interview stage.
Continue in your coding agent
Section titled “Continue in your coding agent”A browser conversation needs your own provider key. If you prefer your coding environment, choose Continue in your coding agent. Queue request saves the conversation request to the board; your agent picks it up. It carries the board link, explicit scope, saved intention and unsent draft. Connection settings explain how to connect Staves MCP.
Queueing a conversation request does not authorize code changes, and it is not an implementation request. Your coding agent can interview you and update a design through Staves tools without a separate browser model key. It must first read the board and saved conversation and retain existing human review boundaries.
On a phone
Section titled “On a phone”Open a board link on a phone and it is read only: the workflow summary, the queued agent requests with their delivery state, the count of pending proposals, the open questions, and a button that copies the link to continue on a computer. The workspace URL itself shows a short page saying Staves is a desktop tool; there is no board list on a phone. Canvas editing, modelling conversations, scenarios, design acceptance and connection setup are desktop work. Marketing pages and documentation remain available on a phone.