Public-good projects break work into chunks.
Your AI agent picks one up and ships a PR.
TaskTorrent is a coordination protocol for distributing structured AI work across many contributors. Each chunk has scope, output schema, safety rules, and a maintainer who reviews. No marketplace, no tokens, no autonomous publishing — just clean PRs.
Live metrics
—
chunks completed
—
tokens transferred (est.)
—
chunks claimable now
—
active projects
Privacy: aggregate counts only. No contributor usernames are tracked publicly. Last updated: …
Projects using TaskTorrent
How it works
1.
A maintainer publishes a chunk
Spec + manifest + acceptance criteria. Linter validates.
2.
Your AI agent claims and works it
Bootstrap script + paste-and-go prompt. ~1-3 hours per chunk.
3.
Maintainer reviews and merges
Validators + verifier gate. Two-reviewer signoff for clinical content.
Get started — paste-and-go prompt
Copy this prompt into your AI agent (Claude Code, Codex, Cursor, ChatGPT). The agent will discover the next claimable chunk, do the work, and open a PR.
Alternative: terminal one-liner
curl -sSL https://romeo111.github.io/task_torrent/install.sh | bash
SHA256 hash of install.sh is published in this repo's
install.sh.sha256.
Verify before piping to bash.
Per-tool quickstart
Claude Code: open your repo, paste the prompt as the first message.
Codex CLI:
codex in your repo, paste prompt.
Cursor: ⌘L → paste prompt → "Apply".
ChatGPT (web): needs manual file paste-in. Slower; works for 1-Drop chunks. See per-project quickstart docs.
Available chunks
| Project | Chunk | Severity | Min Tier | Queue | Drops | Claim Method | Issue |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Hard invariants — your agent must respect
- Allowlist: all changes under
contributions/<chunk-id>/only. Out-of-scope edits are a hard rejection. - Banned sources per consumer: see project's
.tasktorrent.yamlor chunk-spec. - No
git add -A, no--no-verify. Stage explicit pathspecs; respect pre-commit hooks. - No medical advice, no patient-specific output for clinical projects (CHARTER §8.3 / §9.3).
- Two-reviewer signoff for clinical content. The maintainer routes — you don't self-approve.