the-black-schwarm

A GitHub-native live dashboard and recursive Qwen agent swarm orchestrator powered by Ollama Cloud.

Current state: the control-plane code, secure setup, dashboard, GitHub audit primitives, recursive scheduler, model-key isolation, a fail-closed Qwen runner primitive, and a tested in-process swarm MCP broker core exist. Public runs stop before worker dispatch because no authoritative scheduler assignment, trusted Git workspace, or port-7331 sidecar is wired. Recursive scheduler dispatch, the actual sidecar and durable broker ports, GitHub mutation/audit/review loops, and live Boss chat remain P0. No hosted deployment or real model/GitHub/device run has been proven; the fixture is visibly a demo.

The product is intentionally narrow: connect GitHub, provide an Ollama Cloud key, give the supervisor a goal or root issue, and watch a bounded hierarchy of autonomous coding agents plan, implement, review, fix, and hand over one exact candidate for human testing.

Product contract

• GitHub is the durable engineering record: issues, branches, commits with explicit provenance and signature state recorded exactly as observed, PRs, reviews, checks, and an append-only audit ledger. Commits are signed where repository policy requires and the actual creation path proves it.
• Qwen Code runs as an unprivileged user inside isolated Cloudflare Sandboxes against glm-5.2 through an application-owned model proxy.
• A Cloudflare Agent coordinates live state; a Workflow owns durable long-running execution and retries.
• Every agent may spawn scoped child agents within configured depth, concurrency, and budget limits.
• Every task declares an integer token estimate and is rejected above the configured cap, 50% of the configured 976000-token model context, or 200000 tokens. Larger goals are split into parallel-safe work before claim; hosted concurrency defaults to 8 and is currently capped at 12.
• Agents run autonomously and ask the user only for genuine human-only actions.
• The dashboard exposes structured decisions, evidence, messages, tool summaries, tests, and GitHub links—never hidden chain-of-thought or secrets.
• The final Ready for <human> live test gate is derived from evidence at one pinned candidate SHA.

The first dogfood target is the Apple Passwords → Bitwarden iOS import → encrypted sync → Bitwarden Android provider → fresh Nuri PRF recovery journey. The imported object is the same passkey credential material, not a cached PRF output.

Local development

Prerequisites: Node.js 22+, npm, and Docker (required by Cloudflare Sandbox local development).

npm install
npm run dev

Keep secrets in .dev.vars; never commit them:

GITHUB_APP_ID=...
GITHUB_APP_CLIENT_ID=...
GITHUB_APP_CLIENT_SECRET=...
GITHUB_APP_PRIVATE_KEY=...
GITHUB_APP_WEBHOOK_SECRET=...
CREDENTIAL_ENCRYPTION_KEY=...
SETUP_COOKIE_SIGNING_KEY=...

The user enters the Ollama Cloud key in the hosted setup UI. It is encrypted server-side. Sandboxes receive only a short-lived, run/agent/fence/sandbox-bound proxy capability, never the provider key.

Evidence gates

npm run check
npm test
npm run build

See AGENTS.md for the charter inherited by the supervisor and every descendant agent.

The autonomous root prompt is docs/start-issue.md. The executable parallel work board is docs/issues/INDEX.md; its issue bodies are designed to run from the GitHub issue URL alone.