Automatically continue Paseo agent work on a fallback provider after quota or rate-limit failures
npmjs · Paseo 0.9+
paseo plugin add npm:paseo-continuity@0.2.1GitHub · Paseo 0.8 fallback
paseo plugin add keefeere/paseo-continuity --ref 063b7e272ee1946f05e9a4845d239821aa02a049Git security status and fallback installation are pinned to commit 063b7e272ee1.
From the plugin's README
Requires Paseo 0.10.1 or later. Enable plugins under Settings → Plugins, then:
paseo plugin install npm:paseo-continuity
README
Provider failover for Paseo. When an agent stops because its provider has exhausted quota or hit a rate limit, Continuity creates a fresh agent on the next configured provider and gives it a bounded copy of the conversation so work can continue without asking the failed provider to produce a handoff.
Each transition stays in the same workspace. The successor gets a provider-prefixed title such as
● Codex · Fix authentication, chain labels for discovery, and a prompt containing the relevant
timeline. The old chat gets a transition card, while the Continuity chain workspace panel links
the related chats.
Requires Paseo 0.10.1 or later. Enable plugins under Settings → Plugins, then:
paseo plugin install npm:paseo-continuity
# or from GitHub
paseo plugin install github:keefeere/paseo-continuity
Plugins are trusted, unsandboxed code. Continuity runs in the Paseo daemon and can read agent timelines and create agents in their workspaces.
Open Settings → Plugins → Paseo Continuity. The fallback chain accepts one provider per entry, optionally with a model and mode:
codex:auto
claude:auto
gemini:auto
The safe defaults react only to quota and rate-limit failures, bound transferred context, redact common secrets, skip unavailable providers, prevent duplicate successors, and stop after the configured number of consecutive transitions.
Use /continuity or the Command Center action to test or trigger a transition manually.
The pill shows how much quota the current provider has left (its tightest window, e.g.
Codex 23%). At or below the Warn when remaining quota drops to threshold it shows ⚠ and
suggests compacting and moving. Pressing it opens a chooser of the other providers in your chain,
each with its own remaining quota. Compact & move writes a condensed, redacted handoff to
.paseo/continuity/ (self-ignored by git) and starts the chosen provider on it. Turn on Use LLM summary
in settings to have a separate provider/model (for example a cheap or local one) write a summary
that is placed in front of a short verbatim tail; if it fails or times out, the plain transcript
is used. If you ignore the
warning, nothing changes: automatic failover still happens when the provider actually fails.
Automatic transitions require a fallback provider that is configured and ready in Paseo. A transition creates a new agent/chat because the current public plugin API cannot replace the provider of an existing agent.
npm install
npm run typecheck
npm test
paseo plugin install "$PWD" # first time
paseo plugin reload paseo-continuity
paseo plugin logs paseo-continuity
To release, bump the version and push the tag. GitHub Actions publishes to npm through trusted publishing, and Paseo Cafe picks up the new version:
npm version patch # or minor; commits and tags vX.Y.Z
git push --follow-tags
MIT
Scanned 15 Oct 2026, 12:31 UTC from keefeere/paseo-continuity.