prun

Featured

Parallel delegation fan-out. The Claude session coordinates (on whatever Claude model is currently selected, e.g. Opus or Fable) while task units run in parallel on workers (never on the coordinator). Codex (`codex exec`, a separate abundant account) is the prioritized default; Sonnet is reserved for units needing Claude-session-internal capabilities (MCP/email tools, Artifacts, cross-vendor web verification), with the orchestrator deciding per unit. Units may read or write code; workers never commit or push, and the session plus the user are the final integration gate.

AI & Automation 244 stars 26 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 88/100

Stars 20%
80
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# prun (parallel run) ## Overview `prun` fans a task out into independent units that run in parallel on separate-quota or in-session workers, while the Claude session only coordinates. Workers are **Codex** (`codex exec`, a separate abundant account, frontier model) and **Sonnet** subagents (inside the Claude session). **Codex is the prioritized default**: its quota is separate from the Claude plan and its current model (gpt-5.6 tier) is strong on hard reasoning and code, so most units go to Codex. **Sonnet is reserved** for units that need something the Claude session uniquely provides (see the Executors rule). The coordinator decomposes the task, dispatches the units, gathers their results, reviews their diffs, and integrates. It never runs a unit itself. The orchestrator picks the executor per unit; when in doubt, Codex. A Codex unit runs through the separately authenticated Codex/OpenAI account, so the worker run does not draw on the Claude plan at all. A Sonnet unit and the Claude coordinator both consume the current Claude account's quota; the exact split across models and weekly buckets depends on the plan and on active promotions and shifts over time, so check Settings > Usage before relying on any model-specific split. Codex is the default because its worker run is outside the Claude plan; keep Sonnet units targeted because they draw Claude-side quota. ## Relationship to the native Workflow tool The native Workflow tool fans a task out across **Claude** subagent...

Details

Author
yzhao062
Repository
yzhao062/anywhere-agents
Created
4 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

suede-codex-fleet

Claude-directed parallel OpenAI Codex CLI worker fleet for bulk generation. Use when a job is high-volume, well-specified, and splits into independent worker-sized tasks (content batches, test generation, bulk refactors) and Codex CLI is installed and logged in. Claude decomposes, briefs, spawns codex exec runs in parallel, and review-gates every output. Workers are always codex exec processes billed to the user's OpenAI subscription — never substitute Claude subagent fan-out on any model, and halt rather than fall back if Codex CLI is unavailable. NOT FOR: multi-lane Claude agents coordinating one complex change (use suede-agent-teams); low-volume, judgment-dense copy Claude should write itself (use suede-copy or johnny-suede-write).

135 Updated today
JasonColapietro
AI & Automation Listed

ccc-orchestrate

Cross-runtime Orchestrator/Executor — Fable/Opus writes a goal file, GPT-5.6 Sol (codex) or a Sonnet subagent executes it, Fable/Opus verifies against acceptance criteria before reporting done.

6 Updated today
KevinZai
AI & Automation Listed

manage-foreman-agents

Manage background Claude Code or Codex implementation work through the Foreman MCP tools. Use when Claude Code or Codex needs to create goals, delegate isolated Git-worktree tasks, choose a provider, model, or effort level, monitor structured progress, decide routine approval requests, escalate dangerous actions to the user, review diffs, request rework, accept results, or create and review reusable multi-phase workflows.

0 Updated 1 months ago
marcelsud