alethe-orchestrate

Orchestrate coding agents, and prove it was worth it.

English · Português (BR)

npx skills add Kc1t/alethe-orchestrate-skill

/plugin marketplace add Kc1t/alethe-orchestrate-skill
/plugin install alethe-orchestrate@alethe

codex plugin marketplace add Kc1t/alethe-orchestrate-skill
codex plugin add alethe-orchestrate@alethe

1. Install with the command above.
2. /alethe setup checks which agent CLIs you have and whether they are logged in, lists their models, and proposes three profiles: base, savings and aggressive. Nothing is saved until you approve.
3. /alethe always (optional) keeps it on in every project, so you never type /alethe again.
4. Ask for the work: /alethe move the billing endpoints to v2, or just ask in plain words while it is on. The lead picks a playbook, previews the plan and runs the workers.
5. /alethe status while it runs, /alethe stop to stop it.
6. /alethe report when it is done: what each worker did, why, and what it cost. /alethe mark <worker> used records what you kept.

Type them after /alethe.

/alethe help lists the rest.

With always or on, every prompt reminds the lead of your goal and rules, and it decides per request whether to hand work off.

It joins halfway through another skill's workflow: the spec and the diff so far become the plan.

A playbook is a starting point. skip, add, switch and freeform change it between waves, and the report lists every change with its reason.

Agent	CLI	Read-only work	Writing	Resume	Reports
Claude Code	claude	plan permission mode	acceptEdits	✓	Tokens and cost
Codex	codex	read-only sandbox	workspace-write sandbox	✓	Tokens
Antigravity	agy	plan mode	accept-edits mode	✓	Tokens
Kimi Code	kimi	Contract, checked afterwards	Prompt mode, in its own worktree	✓	Nothing
Any other CLI	your adapter	Contract, checked afterwards	Its narrowest write flag		Whatever its output carries

Any other CLI with a non-interactive mode, such as Kiro, Copilot CLI or Gemini CLI, runs as a custom worker.

• Real spend, never estimated: tokens and cost as each CLI reported them, split between used and discarded results.
• Enforced limits: budgets per wave and per orchestration, a hard cost cap on Claude workers, no subagents.
• Never runs your quota dry: it reads Claude and Codex usage before every wave, refuses to start workers past a stop line, and asks you, with options, before it would spend past it.
• Lean, checked workers: no MCP servers in Codex and Claude workers, and git catches a read-only worker that wrote.
• Easy to audit: Python's standard library only, no shell, no network, no install scripts.

/alethe report html opens the same report as a page: a routing map from each wave through the lead to the providers it used, with each one's share of the tokens, then the workers and what is left to do.

Orchestration report

Check the report on real CLIs, playbook research, 1 wave, 2026-10-18 21:20 to 21:20

• Result: 2 of 2 workers succeeded
• Time: 16s running, 29s of worker time
• Tokens: 108,820 reported, 65,836 of them from cache
• Cost: $0.16 reported by claude; codex reports no cost
• Lead context: 5.0 KB of worker transcripts stayed on disk, 595 B of results to read

Worker	Role	Ran on	Mode	Status	Time	Tokens	Cost
claude-haiku	cheapest Claude model for a one-line answer	claude, haiku	read	succeeded	12s	76,160	$0.16
codex-low	default Codex model at low effort	codex, default model, low	read	succeeded	16s	32,660	-

<folder>/
├── budget.json              limits for every wave, optional
├── 01-explore/
│   ├── state.json           the batch at a glance, live while it runs
│   ├── plan.json            the resolved plan, without task text
│   └── workers/<id>/
│       ├── prompt.txt       the brief the worker received
│       ├── result.md        its final answer
│       ├── outcome.json     status, failure kind, metrics, tripwire
│       ├── diff.patch       what a writer changed
│       ├── mark.json        used, partial or discarded, optional
│       └── stdout.log, stderr.log
└── 02-build/

Video	What you will see
	Stop Using One AI Agent at a Time: Orchestrate AI Agents A practical introduction to coordinating several AI coding agents, and to the git worktree isolation that keeps them out of each other's way. Kauã Miguel - Dev · Portuguese

scout-then-build: cheap read-only scouts map the code, then one worker writes the change. /alethe editor opens your own playbooks this way, as one offline page where you can switch profiles, simulate quota and edit a step, then copy the YAML back. It works without Python too.

playbooks:
  scout-then-build:
    name: Scout, then build
    goal: Cheap read-only scouts map the code; one standard worker writes the change.
    pickWhen: Unfamiliar code with much to read and little to write.
    saves: Scouts hand back short summaries instead of raw files filling your context.
    avoidWhen: You already know which files change.
    next: review-gate
    phases:
      - id: brief
        role: planner
        who: lead
        tier: strong
        readOnly: true
        does: Name the areas to map and send one scout per area.
      - id: scout
        role: scout
        tier: cheap
        readOnly: true
        workers: 4
        runner: research
        does: One area per scout; keep each slice well under 100K tokens.
        returns: A summary under 1.5K tokens with file:line pointers.
        gate: The scout reports agree.
      - id: settle
        role: checker
        tier: standard
        effort: high
        readOnly: true
        runner: economy
        after: scout
        if: conflict
        then: recheck
        does: Settle only the contradiction, from the cited lines.
      - id: plan
        role: planner
        who: lead
        tier: strong
        readOnly: true
        does: Turn the summaries into one concrete change plan.
      - id: build
        role: builder
        tier: standard
        readOnly: false
        runner: economy
        does: Implement the plan.
        returns: Changed files, checks run, failures and risks.
        gate: Checks pass.
      - id: fix
        role: fixer
        tier: strong
        readOnly: false
        runner: economy
        after: build
        if: checks-failed
        then: recheck
        does: Fix from the failure excerpt and the diff.

MIT, see LICENSE. The Alethe name and logo and the vendor marks belong to their owners. Part of Alethe · Changelog · Issues

(back to top)