Workflows

A workflow is a short list of steps that Fleet runs for you. Each agent step is an ordinary session with its own agent, model and, if you like, skill. Fleet moves the run from one step to the next, which costs no tokens, and stops wherever a step asks you.

A run uses one new worktree and one branch. Every step works in it.

1. Open Settings → Workflows and switch Workflows on.
2. A Workflows item appears in the rail.

Workflows run on OpenCode, OpenCode 2 and Claude Code. See What works where. On Claude Code, a step’s agent setting is ignored, because Claude Code has no agents to pick from.

• Build a feature turns a sentence into a reviewed pull request. It can start with an optional Design step, then writes a plan and stops once so you can approve it. It then implements, reviews, optionally checks that the app runs, and opens the pull request.
• Fix a bug finds the root cause first, stops for you to agree with it, then fixes it with a test that fails first, reviews the fix and opens a pull request.

1. Choose Workflows in the rail and pick a workflow from the list.
2. In the Run box, choose the repository and base branch, and describe the task. This is the run’s request.
3. Switch on any optional steps you want. They are off unless you do.
4. Choose Run.

The run appears as a group in your session list. Each step is its own session in the group.

When a step asks you, such as Approve the plan, the run stops and shows Needs you. Answer on the card in the conversation. Choose End run at any time to stop Fleet moving the run on. The sessions it made stay as ordinary sessions.

If Fleet restarts, a run carries on from where it was. A run waiting on you keeps waiting.

Switch on Check with me in the Run box and every agent step waits for you before the next one starts. You can talk to the agent in that step for as long as you like, then move on. You can change it from the run’s header while the run is going. It applies from the next step.

Steps ask for a role, not a model: strong for judgement such as design and review, standard for writing code, and fast for short tasks. In Settings → Workflows, Model roles maps each role to one of your models, for each harness. A role you haven’t set uses your default model. The Models menu in the Run box changes them for one run only.

Your workflows are files in the repository, one each, in .weave/workflows/. People you work with get them with the code.

• New workflow starts with a single step. Duplicate to this repo copies a built-in one. Both make an uncommitted file in your checkout.
• The designer shows the steps top to bottom. Use + to add a step that runs an agent, or a You decide step that asks you to choose. Switch to File to edit the YAML directly.
• A step can send work back to an earlier step. Set a limit on how often, and the run asks you where to go once it is used up.
• Try it runs the saved file.

A run keeps the workflow it started with, so saving doesn’t change runs in progress.

name: Dependency bump
description: Bumps the dependencies and checks nothing broke.
steps:
  - id: bump
    title: Bump
    model: standard
    prompt: |
      The request: {{request}}
      Bump the dependencies. Commit the lock file.
    outcomes: [done]

Put {{request}} in every agent step’s prompt. Each step is a new session and knows only what its own prompt says.

• Save as workflow… in a session’s menu turns the process that session followed into a draft. It is only offered on harnesses that can answer without adding to the session.
• New workflow → Describe it drafts one from a sentence.

The draft opens in the designer, unsaved. Nothing is written until you choose Save.

In the Library, choose Repeat on a schedule… on a workflow. This opens a new automation with the workflow filled in. Your automation’s message becomes the run’s request. Check with me is always off for these, because nobody is watching, but a You decide step still stops the run under Needs you.

A run never stacks on one that is still going or waiting on you. That firing is Skipped, with the reason.

• Automations: run a workflow every week.
• What works where: which harnesses can run workflow steps.
• Built-in skills and Memory: the skills workflow steps use.