Creator / AI Workflow Builder· 2026

Orca Fleet: An Agentic Workflow for Running a Fleet of Claude Code Sessions on One Project

ProductivityClaude CodeAgentic WorkflowsPythonClaude SkillsOpen Source

Overview

Orca Fleet is a compact orchestrator for Claude Code. One session leads, the others build or check, and it keeps the whole fleet moving by itself. I use it for my own sprints: an orchestrator, a few lanes building features and checkers looking at what was merged, all on one project, each in its own Claude Code session.

One orchestrator, lanes, checkers, two crons and handovers.

The roles

One orchestrator, started with /orca-fleet:conduct. It plans and routes the work, keeps the orders file and the merge queue, and merges only what your project's rules file allows. Merge rights never come from the plugin itself.

Lanes, the builder sessions, started with /orca-fleet:join-lane. Each one builds one stream of work, pushes once per finished change, and reports back in one line when a change is ready to merge. Anything new it runs into, a decision, a question or a deferral, goes into the open items list in the same turn.

Checkers, started with /orca-fleet:join-checker. They work through the preview ledger, where every merged change people can see gets a row, and check each one once, the way a person would, with the test accounts your project config names. They write pass or fail with what they saw, and send a fail straight to the orchestrator.

What it does by itself

The orchestrator runs two crons. By default a status round runs twice an hour, at 13 and 43 minutes past, and reads every session's context: at 70% it tells that session to write its handover note, at 85% to hand over. A nudge round every 15 minutes wakes any lane that went idle with work left, and leaves sessions that are waiting on you alone. The minutes and the thresholds are in the project config.

A handover is a fresh session, never a fork. A session near full context writes a note from its role's template, with the branch, PR numbers and the exact next step, and starts a fresh session with that note as its first prompt. The new one reads only the note, reports in, and tells the old one: took over, you can close. Each successor gets the next number, so Lane 2 becomes Lane 2 #2, then #3.

The orchestrator hands over too. When its own context fills or a new sprint starts, a fresh orchestrator reads the last one's note, tells the old one to stop its crons so two never run at once, and tells every session where to report now. Sprint after sprint, the plan carries on. The session I built Orca Strator in did exactly this: at 88% context it wrote its handover note, and a fresh session read that one file and carried on.

Everything is on file: an orders file for instructions to every session, the merge queue, the preview ledger for the checkers, an open items list so nothing raised in a chat gets lost, a handoff template for each role, and one config file per project that sets the crons, the thresholds, where checkers sign in, and which rules file says who may merge and what always needs a person.

Install

Orca Fleet is part of Orca Strator, free and open source (MIT) in the claude-plugins marketplace on GitHub. Install the Orca Strator bundle, which brings in Orca Fleet and orca-peers, the plugin it uses to find every session's address and context level, then run /orca-fleet:conduct in the session that should lead. It needs Claude Code 2.1.310 or later. The fresh session for a handover opens in a new Terminal.app window on macOS; elsewhere it copies the command for you to paste.

bash
/plugin marketplace add mutlumehmet/claude-plugins
/plugin install orca-strator@mehmetmutlu
/orca-fleet:conduct
Open source on GitHubmutlumehmet/claude-plugins/plugins/orca-fleet