NeuralCodeDOCS
Configuration

Workflows

A workflow is a saved, named pipeline of agents. Build it once in Settings, then apply it from the composer in one click — it selects the agent steps in order so your next message runs straight through them.

Back to app
General
Models
Agents
Workflows
MCP servers
Commands & Skills
Appearance
Git
Account
About
v0.1.0-beta.1

Workflows

Save a reusable pipeline of agents. Pick one from the workflow button in the message box to apply its steps in one click.

Ship itbuilt-in
Plan → build → review → write tests
1. plan2. goal3. review4. test
Safe refactorbuilt-in
Refactor → test → review (no behavior change)
1. refactor2. test3. review
Review & hardenbuilt-in
Review the diff, then add tests
1. review2. test
Settings → Workflows: each workflow is a named pipeline of agent steps. Built-ins ship ready to use; add your own with New workflow.

Workflows vs. agents#

A pipeline is the ordered set of agents you pick in the composer for a single task. A workflow is that pipeline saved with a nameso you don't have to rebuild it every time. Applying a workflow simply selects its steps in the picker — from there it runs exactly like any other pipeline, each stage carrying its own model, thinking budget, and permission mode.

The built-in workflows#

NeuralCode ships three built-ins covering the most common sequences. They can be applied as-is, and editing one saves a copy you can tweak — the original stays put.

WorkflowStepsFor
Ship it/plan → /goal → /review → /testTake a feature from idea to tested change.
Safe refactor/refactor → /test → /reviewRestructure code without changing behavior.
Review & harden/review → /testAudit an existing diff and add coverage.

Applying a workflow#

When you have at least one workflow, a workflow button appears in the composer toolbar. Open it, pick a workflow, and its steps drop into the agent chip row — ready to send.

Workflows — applies a pipeline of agents
Ship itPlan → build → review → write tests · 4 steps
Safe refactorRefactor → test → review (no behavior change) · 3 steps
Review & hardenReview the diff, then add tests · 2 steps
Refactor the auth module and ship a PR…
Opus 4.8
The composer's workflow dropdown — choosing one applies its agent steps to the message in a single click.
Note
Only enabled agents are applied. If a workflow references an agent you've since disabled or deleted, that step is skipped and the rest still run in order.

Creating your own#

Manage workflows in Settings → Workflows.

  1. 1
    New workflow
    Click New workflow, then give it a name and a short description (e.g. “Plan → build → review → test”).
  2. 2
    Add steps
    Add agents from the picker; they run top-to-bottom on your task. Reorder or remove any step. Only enabled agents are available.
  3. 3
    Save
    Save it — a name and at least one step are required. It now shows in the composer's workflow dropdown for every workspace.
Order matters
The same advice as ad-hoc pipelines applies: planning and clarification first, edits in the middle, and a read-only /review or /prlast. Delete the custom workflows you no longer use — built-ins can't be deleted, only copied.