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
Competing backend-primacy claims, and the default backend's single-agent limitation isn't where the reader chooses #338
The docs give competing claims about which backend is primary, and the default backend's single-agent limitation is not surfaced where the reader actually chooses a backend.
Evidence (file:line)
docs/QUICKSTART_SBX.md:3 — "Recommended for federal users" (points at the non-default sbx)
README.md:449 — "msb by default"
msb.sh:2597 — the opencode-only fact (default backend supports a single agent) is buried in a code comment
The KNOWN_FAILURE_MODES agent list is unscoped, so it does not clarify which agents apply to the default backend.
Suggested fix
Add one authoritative "which backend" section that resolves the primacy conflict.
Surface the default-backend (msb) agent support at the point where the reader chooses a backend, not in a code comment.
Surfaced via an automated audit (Fable) against a public clone; validated against main 2026-08-19. AI-assisted (OpenCode).
Activity
wz-gsa commentedon Aug 20, 2026
Addressed in open PR #345 (awaiting review). Grooming 2026-08-20.
docs: fix first-day default-path accuracy (USAi, backend primacy, dea…
wz-gsa commentedon Aug 20, 2026
Fixed on main by merged PR #345 (msb-is-default primacy clarified; msb opencode-only auto-install surfaced in BACKEND_GUIDE limitations).
docs: reconcile backend-primacy framing + refresh CONTEXT-GUIDE.md
docs: reconcile backend-primacy framing + refresh CONTEXT-GUIDE.md
docs: reconcile backend-primacy framing + refresh CONTEXT-GUIDE.md (#364