Skip to content
Weaveweave / fleet
Install Fleet
Docs/Harnesses/What works where

What works where

What each harness can do in Fleet, side by side. Steering, forking, subagents, workflows, canvas pages, images, the agent picker, profiles and sign-in for OpenCode 2, OpenCode, Claude Code, GitHub Copilot and Pi.

The conversation, the list, the review panel and the worktrees work the same on every harness. These things depend on the harness. This table was checked against Fleet 0.57.0.

OpenCode 2 OpenCode Claude Code GitHub Copilot Pi
Pick a model ✓ ✓ ✓ ✓ ✓
Pick an agent ✓ ✓
Slash commands and skills ✓ ✓ ✓
Reopen a session later ✓ ✓ ✓ ✓ ✓
Steer a running turn ✓ ✓ ✓ ✓
Compact the conversation ✓ ✓ ✓ ✓
Fork a session ✓ ✓
Side conversation (/btw) ✓ ✓
Run a shell command (!git status) ✓ ✓
Subagents as their own sessions ✓ ✓ ✓
Workflow steps ✓ ✓ ✓
Pages and diagrams beside the chat ✓ ✓ ✓ ✓
Agent reads a session you link with @ ✓ ✓ ✓ ✓
The agent can use Fleet’s browser ✓ ✓ ✓
Paste images ✓ ✓ ✓ ✓
Permission levels (Settings → Permissions) ✓ ✓ ✓ ✓
Profiles ✓ ✓
Provider sign-in in Fleet ✓ ✓

Notes

Section titled “Notes”
  • Steer a running turn. The agent reads your message at its next step instead of waiting for the turn to end. On OpenCode 2 and Claude Code, Enter steers and Queue waits for the end. On OpenCode, Enter queues and Send now steers, and the agent reads it at its next model call. GitHub Copilot steers, but Enter queues, as on OpenCode.
  • Fork. Fleet copies the conversation up to the last finished turn into a new session. Claude Code and Pi can’t do this yet.
  • Subagents as sessions. A subagent’s work gets a session of its own, under its parent. On Claude Code you can read it, but not send it a message.
  • Workflow steps. A Fleet workflow is a short list of steps that Fleet runs as sessions, one after another. It can only run on a harness that can report a step as done. Workflows are experimental and off until you turn them on in Settings → Workflows.
  • Pages and diagrams. The agent draws a page or a diagram in a tab beside the chat. These need Fleet’s tools, which Pi doesn’t get. A session you link with @ reaches Pi as a short recap instead. The experimental Choose on a page setting works with OpenCode and Claude Code, and GitHub Copilot needs a newer weave-copilot for it.
  • Permission levels. Fleet turns your level into the harness’s own rules and asks you about the rest. Pi has no levels.
  • Profiles. Named harness config you keep in Fleet and pick for a session.
  • Pi. A Pi session starts with your first message, and Fleet shows what Pi reports. It has no agents, commands, images, subagents or workflows.

Choose a harness says how to install each one.

Where next

Section titled “Where next”