sonder-agents-and-fleets

Operate Sonder autopilot runs, orchestrator fleets, model fanout, and multi-PC Ollama worker pools.

6|3|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Krilliac/Sonder-runtime --skill sonder-agents-and-fleets-krilliac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sonder-agents-and-fleets
Source: https://github.com/Krilliac/Sonder-runtime/tree/main/.claude/skills/sonder-agents-and-fleets
Command: npx skills add https://github.com/Krilliac/Sonder-runtime --skill sonder-agents-and-fleets-krilliac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running autonomous and parallel agent work in Sonder involves layered systems—autopilot runs, master orchestrator fleets, model fanout, and a multi-PC Ollama worker pool—each with its own lifecycle states, capacity limits, cancellation semantics, and failure modes. This Skill provides the verified operational knowledge to start, monitor, cancel, retry, and troubleshoot all of them without guessing at internal behavior. ## Core Features & Use Cases - Autopilot run management: Start, pause, resume, and cancel restart-safe autonomous goal runs with hard bounds on cycles, checkpoints, and task output, including crash recovery via explicit resume of interrupted runs. - Fleet orchestration and capacity planning: Delegate parallel subagents through master_orchestrate with computed worker slots based on CPU, RAM, GPU VRAM, and Ollama batch width, plus cooperative cancellation and idempotent retries through the durable fleet ledger. - Protected objective runs and inference pooling: Enforce provenance contracts requiring tool evidence for fleet claims, run model fanout across local and cloud models, and configure a multi-PC Ollama worker pool with TLS validation, circuit breakers, and pre-response failover. - Use Case: A user says "use 24 workers to audit this repository in parallel." The Skill guides checking master_capacity for the real worker slot bound, launching a fleet-mode run confined to the project root, monitoring with master_status, and cooperatively cancelling or retrying agents as needed. ## Quick Start Ask the assistant to check fleet capacity with master_capacity and then start a delegated fleet run confined to your project root using master_orchestrate.

Frequently Asked Questions about sonder-agents-and-fleets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel agents with a specific worker count in Sonder?

Use master_orchestrate with mode fleet or delegate and pass worker_cap, or include one unquoted affirmative phrase like "use 24 workers" in the task. Check master_capacity first to see actual worker_slots and what bound them, since CPU, RAM, VRAM, and OLLAMA_NUM_PARALLEL all clamp the result.

How do I recover an autopilot run after a crash or restart?

Check state with autopilot_status or the REPL /autopilot status, review any mid-write workspace changes, then explicitly resume or cancel the run. Tasks that were running at crash time become uncertain and are intentionally never replayed automatically.

Why does cancelling a fleet agent not stop it immediately?

Cancellation is cooperative: the cancel flag is checked before each model call, so an in-flight Ollama call finishes and its result is discarded. The master_cancel output reports active model calls awaiting return for exactly this reason.

Can Sonder fleets use cloud models for delegated tasks?

Protected objective runs require local worker and audit tiers so task text and repository evidence never route to hosted models. Autopilot refuses cloud tiers outright, and cloud fanout requires SONDER_ALLOW_CLOUD=1 with no automatic retry of failed cloud calls.

How do I set up a multi-PC Ollama worker pool?

Set SONDER_OLLAMA_WORKERS to semicolon-separated worker origins and SONDER_ALLOW_REMOTE_OLLAMA=1, then run preflight and serve. Non-loopback origins require https, an explicit port, no inline credentials, and each worker must have the exact model tags pulled.

Why was my protected fleet result rejected?

Protected runs require an === TOOL EVIDENCE === block with steps from file_read, file_read_range, text_search, or script_search. Negative claims without target evidence, repeated identical evidence blocks, or a target file that changed mid-call all cause rejection.