You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dispatch --go fails spawning into a project with no remembered provider: HTTP 503 codex models #2
The intake lane itself is configured correctly (claude-code / claude-sonnet-5, confirmed via Settings → Plugins → Dispatch), and the preview step (classify + expand) works fine. The failure happens at the actual --go spawn, into whatever project dispatch classified as the target.
bb dispatch failed: HTTP 503: Unable to load codex models to resolve the default. Try again once the host is connected and the provider is ready.
Root cause: the target project (a local-path-only project with no git remote) has no remembered provider/model default. Per bb guide providers, bb's spawn fallback in that case is "the explicitly requested provider or Codex" — so it silently tries Codex. Codex is registered as a provider on this host but has zero models configured (bb provider models codex → "No models available"), so the spawn 503s.
This means bb dispatch ... --go is unusable against any project that hasn't already had a thread spawned with an explicit provider, unless Codex happens to be configured, even when the intake lane and every other provider (Claude Code, pi) are working fine.
Also seen on stable (exact version not confirmed at time of filing), not just nightly.
Repro:
Configure the dispatch intake lane to a working provider (e.g. claude-code).
Ensure the destination project has no remembered provider/model default and Codex has no models configured on the host.
Root-caused this: it's not dispatch doing anything wrong. spawnThread in server.ts intentionally omits providerId/model for the destination thread, relying on bb's own default-provider resolution. That resolution falls back to Codex unconditionally when the target project has no remembered default, with no fallback to another configured provider if Codex itself isn't set up on the host.
Activity
technicalpickles commentedon Aug 22, 2026
Root-caused this: it's not dispatch doing anything wrong.
spawnThreadin server.ts intentionally omitsproviderId/modelfor the destination thread, relying on bb's own default-provider resolution. That resolution falls back to Codex unconditionally when the target project has no remembered default, with no fallback to another configured provider if Codex itself isn't set up on the host.Filed upstream against bb: get-bb/bb#2306