One ConnectUsing One Connect
Canvas and workflows
The canvas is home. Each workflow is a frame holding a typed node graph of agents, issues and steps, and workflows connect to each other directly or through a decision.
What a workflow is#
A workflow ties existing issues and agents into steps. Independent workflows run every step in parallel; collaborative ones follow the connections in dependency order. Every step still goes through the normal assignment, pre-flight, worktree and capacity checks, and the event log owns the workflow's state.
On the canvas each workflow is a frame. Inside it you wire nodes together with typed, coloured ports: a port only connects to a port of the same type.
Nodes#
| Node | Shape | What it does |
|---|---|---|
| Agent | Round | Which agent runs the steps it connects to, with its model and effort. Accepts skills, connectors and other agents it may talk with. |
| Step | Card | Plan, build or review work, run by the connected agent |
| Issue | Pill | The tracker issue a step works on. You can pick one or create it from the node. |
| Designer artifact | Pill | An approved mock revision for the step to follow |
| Skill | Pill | A skill from your library, GitHub or the Anthropic catalog |
| Connector | Pill | Tools from a local MCP connection. Every tool call still needs its normal approval. |
| One Ask | Pill | A question to your project knowledge; its answer becomes context for connected steps |
| Summary | Pill | A plain-language summary of One Ask answers by the bundled local model |
| Note | Pill | A comment on the canvas. Never sent to agents. |
Step kinds#
| Kind | Label | Behaviour |
|---|---|---|
coordination | Plan | An architect step: plans and coordinates, never writes code |
code | Build | Writes code on its own branch |
review | Review | An independent, read-only review of a build step at its exact SHA |
A step's inspector sets its title, the allowed paths (empty means the whole repository), its required checks, a model and effort that override the agent's, and any context to pass along.
Ports#
| Port | Carries | From → to |
|---|---|---|
| Agent | Who runs a step | Agent → Step |
| Issue | The work item | Issue → Step |
| Flow | "After": run order | Step (Done) → Step |
| Design | An approved mock | Designer artifact → Step |
| Skill | Instructions loaded on demand | Skill → Agent or Step |
| Connector | Tools | Connector → Agent or Step |
| Context | Answers and summaries | One Ask or Summary → Summary or Step |
| Talks with | Which agents may message each other | Agent ↔ Agent |
Build a workflow#
- Double-click the empty canvas, or right-click and choose New workflow here. A new frame starts with an Agent node.
- Double-click inside the frame, or drop a connection on empty space, to search for a node. You can also drag from the Node library, or click a library item to add it to the selected workflow.
- Connect an Agent and an Issue to each Step, and connect steps' Done to the next step's After for ordering.
- Choose Follow the connections (dependency order) or Run every step in parallel.
- Save draft to keep editing later, or Run workflow from the frame's menu.
Drafts are edited in place, with undo and redo (⌘Z, ⇧⌘Z) and copy and paste of nodes (⌘C, ⌘V). Right-click a node to duplicate or delete it.
Running, pausing and terminating#
- Run locks the workflow. Its frame shows each step's live status and progress: pending, queued, running, verifying, done, changes requested, blocked, failed or canceled.
- Pause and Resume hold and continue the workflow. Retry step re-runs a failed or invalidated step.
- Terminate… ends a running workflow so it can be changed. Changing it creates a new draft that continues the terminated one: finished steps stay on the original, and a step can carry a pickup point from its previous attempt.
Completion follows evidence#
A step is done only when the daemon recorded evidence for it. A build step needs a verified commit and the required checks at its current branch SHA in the configured check runtime. A review step needs an independent verdict for that exact target.
Completed workflows keep watching. Changed source, failed checks or a stale review remove completion and block the steps that depend on it. Runs already in progress may finish, but their output cannot bypass an invalid upstream step. You retry the affected step and its dependents yourself; nothing finished is silently re-run.
Connect workflows#
Workflows can start one another:
- Then: connect a frame's finished output to another frame's start. When the first finishes, the second starts.
- Decision: add a decision node (Decision · you or Decision · JEV) after a workflow, with a question and 2 to 8 options, each starting a different workflow.
- You decide: the question comes to your inbox when the first workflow finishes.
- JEV recommends: the optional Jev advisor suggests an option. Before it can even recommend, you confirm what it may receive, including an evidence limit of 1 to 24,000 bytes. Letting it pick on its own is a separate opt-in per decision.
Visibility#
Finished or quiet workflows can be hidden. A hidden workflow comes back on the canvas by itself when it reaches a condition you chose: it needs your input, it failed, or it finished. Visibility… in a frame's menu sets these.
All workflows#
All workflows (/workflows) lists every workflow in a table with its status and progress, from the live event log.
Messages inside a workflow#
Agents connected with Talks with can message each other through the project's team inbox, and every message is visible to you. Messages are advice and evidence: they cannot grant approvals or override scope, cost, security or release policies. See Team conversations.