Ultraswarm

ultraswarm

Ultraswarm is a durable multi-worker coding orchestrator for Codex, Claude Code,
Cursor Agent, Grok, and shell usage. One standalone Node runner owns decomposition, worker
routing, process supervision, isolated Git worktrees, adaptive review,
transactional integration, approvals, recovery, and reporting.

What's New In v3.6.0

The run report now ends with an estimated-vs-used token breakdown by CLI, model, and effort, and
the CLI gained onboarding/recovery commands:

- TOKENS BY CLI / MODEL / EFFORT table closes every report — CLI | model | effort | est. |
  used | Δ | attempts, plus a total row. est. is a calibration-informed heuristic: ultraswarm
  prefers the measured per-(CLI, model, effort) average persisted in .ultraswarm/state.sqlite
  (route_calibration, self-correcting across runs) and falls back to a static tier curve (simple
  10k / moderate 30k / complex 75k / expert 150k tokens) until enough runs accumulate. used is
  ONLY structured usage summed across attempts — — when a CLI reports none, never backfilled from
  the estimate (the v3.5.13 honesty invariant still holds).
- Attempts now record the resolved model id, tier, and effort, not just the tier where "model"
  used to live (schema migration v3, additive — existing v2 databases upgrade in place). Failed
  attempts record their burned tokens too, so a rejected retry still counts toward the table above.
  When a CLI doesn't self-report cost, worker spend is now priced from
  config.intelligence.pricing[model] (USD per million tokens; falls back to built-in Claude
  rates, else 0 for an unpriced model) so maxCostUsd can actually bound external worker spend.
- Declarative usage capture widens real token reporting from 2 built-ins to 3. Each registry
  entry can now declare a usage array of {…