0.9.0 Latest release · 9 November 2026

Shipyard. Tools built for your agents, and agents that work together.

Your agents can get tools built for them: describe one, and Crew's coding agents write it, test it and publish it to Flight Deck, which runs it for your agents in a sandbox on Linux. Agents fit in one .captain file now, to back up, move or hand to a client. They hand each other work, answer email meant for them, read any IMAP inbox, learn from your corrections once you approve, share one external memory, and know the goals their work is for. 52 pull requests, #436 to #487.

0.9.0 Also in this release

Asked, remembered, aimed.

Seven new tools make 79 built-in tools per agent (78 in the desktop app): custom_tools, ask_user, colleagues, imap_mail, external_memory, course and image_manipulation.

Upgrade To 0.9.0

Flight Deck first, then every agent.

Console → Updates does it on a deck on a git checkout. jsonschema is now a declared dependency, so install the package again by hand. Agents need the restart for the seven new tools, the Course prompt and the lesson proposals. Then hard-refresh every browser.

On each Flight Deck
cd ~/captain-claw && git pull
pip install -e .    # or: uv sync
# restart Flight Deck, then every agent, then hard-refresh
Two things on by default
# lesson proposals, per agent, in config.yaml
lesson_proposals:
  enabled: false
# agents picking up email that names them, deck-wide
FD_AGENT_MAIL=off
  • Look at what's on by default. Lesson proposals: a small model call on turns that read like a correction, 12 a day at most. Agents pick up email that names them, from the first new mail after the upgrade; switch Pick up email meant for ‹agent› off per agent, and give agents with common-word names a specific name to answer to.
  • Decks without sign-in now apply their console Settings (branding, deck name, Docker), and deleting a user now stops and removes their agents, folders and chats.
  • Custom tools stay off until an admin turns them on. They need git on the host (uv is optional). On Linux, python3 tests/test_flight_deck/test_xtool_sandbox.py says whether the kernel has Landlock.
  • Back up the new data: external_tools/, agent-bundles/ and course.db in the deck's data folder, and bundle_signing_key in its home.
  • The desktop app: Check for Updates…, which also offers 0.9.0 within a minute of starting. New installers are needed only for a fresh install or the new About panel.
  • Devices, BotPort hubs, Captain for Chrome and Captain for Mac need nothing: firmware stays 0.20.4 / PaperColor B 1.0.31, and BotPort keeps protocol 2.

Upgrading to 0.9.0 · New settings · Release notes · Installers on GitHub

0.8.11 5 November 2026

Hold. A message waits while the agent is busy.

0.8.10 5 November 2026

Provisions. A provider and a key, and every tier is set.

0.8.9 4 November 2026

Porthole. The desktop app on Windows.

0.8.8 4 November 2026

Spyglass. Your agents see what you see.

Captain for Chrome sends the page you're on to an agent, and Captain for Mac anything on your screen. On 4 November we also read what test users on the cohort deck ran into; these are the fixes, ten pull requests in all.

The desktop app no longer shows Captain Swarm: its one user is the local admin. Its agents had 69 built-in tools then, every other deck's 70.

Upgrade From 0.8.5 to 0.8.8

Flight Deck first, then every agent.

The same steps take a deck from 0.8.5, 0.8.6 or 0.8.7 to 0.8.8. Console → Updates does it on a deck on a git checkout. Two changes to know first: a Bat run with no cap now stops at $50 (since 0.8.6; FD_BAT_DEFAULT_LLM_USD=0 for none), and public file links expire.

On each Flight Deck
cd ~/captain-claw && git pull
pip install .
# restart Flight Deck, then every agent, then hard-refresh
If Chromium can't start on the server
# once, as root, with the deck's Python
python -m playwright install-deps chromium
  • Captain for Chrome: Flight Deck → Connections → Browser → Download the extension, then Load unpacked.
  • Captain for Mac: the GitHub release or Connections → Browser. It needs a 0.8.8 deck.
  • The desktop app: download Captain once if you're still on the old 2.5 GB app; from 0.8.6 on it updates itself with Check for Updates….
  • Devices and BotPort hubs need nothing: firmware stays 0.20.4 / PaperColor B 1.0.31, and BotPort keeps protocol 2.

Upgrading to 0.8.8 · 0.8.8 settings · 0.8.8 release notes

0.8.7 4 November 2026

Shakedown. A same-day patch.

0.8.6 4 November 2026

Ship's Log. A log of everything they did on their own.

The Line, a way to make agents measurably better at real work, 131 archetypes, and a desktop app that went from 2.5 GB to 75 MB.

0.8.6 release notes

0.8.5 2 November 2026

All hands on deck. Real office files, and a tidier deck.

Coding agents working for you in Crew, a team forged from a plain request in Forge agents, a Taskboard that hands over many tasks at once, and a deck that updates itself.

Updates Console → Updates

A deck that updates itself.

On a git checkout, it follows the branch it's on, so a fork follows the fork. It only moves forward, to the commit you saw.

  1. 1

    Test start

    The new commit runs from a temp folder on a spare port, with an empty data folder and none of the deck's keys. If that fails, nothing has been touched.

  2. 2

    A warning

    Everyone signed in gets a toast, then one they can't close, counting down two minutes.

  3. 3

    Stop the agents

    Mid-turn ones can be waited for, up to 5 more minutes. Crew's workers keep going.

  4. 4

    Pull

    New packages went in before the test start, so you don't run pip yourself.

  5. 5

    Restart in place

    The same process, command line and tmux pane, so it can't lose the environment you started it with.

  6. 6

    Check

    If it doesn't come up, the old commit goes back and the deck starts on that, by itself. Every admin gets an email saying how it went.

Off by default, or Tell me, or Install by itself, where whatever is merged to the branch goes live once it passes the test start. A desktop build or a container is updated the way it was installed.

Upgrade From 0.8.4 to 0.8.5

Flight Deck first, then every agent.

There are no new Python packages, and BotPort hubs need nothing new. This one is by hand; after it, the console does it. Approving someone for Crew trusts them with the server, so read this first. Crew stays off for non-admins until you tick it.

On each Flight Deck
cd ~/captain-claw && git pull
pip install .
# restart Flight Deck, then every agent, then hard-refresh
If you want them
# for Crew: install the CLIs on the deck's host, then
# tick Crew per person on Users, and save logins in Crew → Logins
# new device firmware, from firmware/device
python tools/publish.py <env> --deck https://<deck>

Before you approve anyone for Crew · Upgrading to 0.8.5 · 0.8.5 release notes

0.8.4 30 October 2026

Onboarded, on the board. A deck for people who don't share a machine.

Teach an agent your work and exam it, then see everything it was asked on one Taskboard.

This is containment, not an OS sandbox: an admin's agent still has a shell that reaches the whole host. · The team checklist

Coming from 0.8.3? The 0.8.4 steps take away the tools that run code from non-admins' agents, so read those first. · 0.8.4 release notes

0.8.3 27 October 2026

Plugged in, on the record.

Agent links, your own WhatsApp, a register of every tool call, notifications everywhere, and idle agents that sleep.

0.8.2 Also in that release

Everyone shares. Long answers play through.

Coming from 0.8.1? The hub first, then the decks. · The BotPort guide, from pip install on a Raspberry Pi to the first request between two decks

0.8.1 24 October 2026

A kiosk for everyone. Devices that listen.

Also in 0.8.0

And a few more things

Jev — calibrated judgments

Jev (TypeSafe AI) answers yes/no, choice and rubric questions with probabilities. Each user connects their own key; agents get a jev tool, flows a tool: jev step, the MCP server jev_ask, and Connections a playground.

Lupa — a research desk on Flight Deck

A standalone B2B research desk built purely on Flight Deck's HTTP API: streams of research with a plan gate, reports with a receipts panel (verdict, confirmed and refuted claims, cost with ROI), standing briefs and a Basna second opinion — plus Kalup, a Pack Studio that turns a desk description into a published vertical desk.

Models and providers

Thinking models stop 400-ing; OpenAI reasoning effort per tier; local servers shrink an output budget their window can't hold instead of failing; Google subscription text through the Antigravity CLI; You.com web search. Agents start fast offline: 75 s → 0.1 s with the Hub unreachable.

Story Integrity Protocol

Opt-in for long-form runs: deterministic checks that can block, model passes that only revise, advisory scores — and a per-tier Weak / fast model checkbox so the pipeline tends a small model instead of trusting it.

Iskra reports

A Reports view has a Deep-Researcher narrate how the village of living beings worked over any period — Quick or Deep, numbers straight from the ledger, saved and readable in a proper reader.

Small things

The Task Planner distributes a reviewed plan round-robin across lanes; chat stays fast on older machines; an archetype grid composes reviewer.legal-style roles from a function and a domain; each user binds their own WhatsApp number; six opt-in Loops & Graphs levers.

0.8.0 release notes · All release notes