Fleet Guard

A Paseo plugin that keeps long-running Claude jobs moving when a session limit gets in the way. Windows, macOS and Linux.

Fleet Supervisor 4 beta · Getting started · How it works

**Beta software:** Fleet Guard is useful today, but it is still young. Keep an eye on important work and report anything surprising.

Fleet Guard watches a root Claude Code task inside [Paseo](https://paseo.sh/). When Claude reports a real session or quota limit, Fleet Supervisor hands the same workspace and task context to the exact provider **and model** you chose—including another Claude model or a model running locally on your PC. It can nudge an unfinished agent, check a premature completion claim, cycle through fallbacks, and return the work to the original Claude task after a cooldown.

Version 4 also adds multi-model review to Paseo itself. **Skeptic Review** sends the latest task context to every configured reviewer; they run independently and in parallel, and the original task receives their conclusions and writes one digest. It runs on **stock, released Paseo** — no patched build, no forked app.

It does **not** bypass limits or share accounts. Every fallback uses its own official CLI, login, permissions, subscription, and quota.

Settings inside Paseo, not a config file

Fleet Supervisor's settings are a Paseo surface, opened from Paseo's sidebar. It asks Paseo for each provider's current model catalog and lets you choose an exact model, priority, model-specific role, review lens, and continuation policy — every key the guard reads. Changes save straight to disk and the running guard picks them up, so nothing has to be rein