worker routingCODEX / IN GOOD COMPANY

A LITTLE HELP. ROOM TO BLOOM.

Good work.In good company.

Bring the goal. Your main agent shapes the work.
Workers investigate, build, check and repair; your main agent keeps judgment and delivery.

Start your first delegation Follow the work

Whole responsibilities · Same-session continuation · Optional ACP collection & recovery

A work order, a folded-ear cat seal, and a returned note with changes and checks
A work order goes out. Evidence comes back.

01 / WORK THAT KEEPS MOVING 0.4 SERIES

A handoff.
And a way forward.

The 0.4 series connects whole responsibilities, worker self-check, help from the main agent and continuation in the original session. The plugin guides cooperation; the optional ACP runner retains execution state, collects returns and supports finite batches.

ONE RESPONSIBILITY, KEPT TOGETHERNative / ACP
  1. MAIN AGENT

    Keep the goal. Shape the work.

    Take an engineering goal, honor the chosen channel, and hand over a whole responsibility with boundaries and completion criteria.

    Goal · Work order · Permissions
  2. WORKER

    Check, repair, and deliver.

    Keep investigation, implementation, self-check and ordinary repairs together. Bring back progress and a precise question when a key judgment is missing.

    Investigate → Implement → Check → Repair
  3. MAIN AGENT

    Read the evidence. Move forward.

    Inspect artifacts, coverage and conflicts; check concrete doubts. Integrate supported work for delivery, or supply the judgment needed to continue.

    Artifacts · Check evidence · Final delivery
A little help. Then back to the same worker.

Return decisions, added constraints or specific rework to the original session; keep useful execution with its worker.

This is the cooperation policy delivered to agents. The main agent judges delegation and acceptance; tiny, nearly finished or solo work can stay direct.
01

Self-check belongs with the work

Workers check, repair and recheck within their scope. The main agent helps with key questions, then returns useful execution to the same responsibility.

02

Read results as they land

Optional ACP delivery collection bounds the return. A finite batch persists settled results item by item; collect reads them while the main agent retains the remaining work.

03

Recover the original execution

Use the original session and receipt to establish state and preserve existing work. Confirm timeout, cancellation and cleanup separately before choosing the next step.

OPTIONAL ACP / FINITE BATCH

The main agent chooses the work. The CLI handles the mechanics.

One order spec authored by the main agent connects preparation, finite execution and incremental collection. One default worker is enough to start; batch only responsibilities already known to be independent.

  1. prepareAssemble ordersGenerate orders and a manifest mechanically; launch no worker.
  2. batchAdmit and executeCheck authorizations and resources, execute this finite batch, and persist each settled result.
  3. collectRead what has landedRead the settled index without waiting for the rest; retain outstanding responsibilities.

The ACP runner retains sessions, receipts and bounded delivery clues. Worker reports, observed runtime state and main-agent acceptance remain distinct. Serialize a shared HOME when its concurrency safety is unknown.

One default worker is enough.

Honor your choice of native Codex or external ACP channel. Models, accounts and routes stay yours; Dispatch can show ACP receipts when needed.

Explore the architecture

02 / DISPATCH — LOCAL FIELD NOTES

See how the work adds up.

Dispatch as usual; the receipts leave a trail. See totals in Home, find projects and their history in Sessions. No extra stamp after every task.

DispatchILLUSTRATIVE DATA · ACP ONLY
A WEEK IN GOOD COMPANY

Good work, in good company.

01 — 07 SEP 2026
24delegated tasks
42worker turns
840Kobserved tokensAttributable usage for 21 / 24 tasks

● Completed 22● Cancelled 2

Activity over time

September 1–7 · Full week42worker turns

Synthetic sample · Worker turns only

A TRAIL YOU CAN FOLLOW

Numbers with a source.
Details stay local.

Browse by Git repository or folder. Follow continuations and runtime records. Missing usage stays unknown.

Read the Dispatch guide
This is a synthetic public example. Your Dispatch runs locally, on demand; private records are never published to this site.

04 / YOUR FIRST HANDOFF

Start with one real task.

Open the repository in Codex and ask its built-in plugin-creator to install Worker Routing. Keep your current main model and provider configuration.

The first-delegation guide Open the GitHub repository
A NOTE TO CODEX
Install plugins/worker-routing from this repository into my personal marketplace.
Keep my current main model and provider configuration.
For updates, use a cachebuster and the normal reinstall flow.

Register the plugin, then start a new session to confirm it is loaded. ACP and the private-context SessionStart hook are separate, optional additions.

Installation, verification & recovery

A FEW THINGS, CLEARLY

A few things to know.

From your first delegation to a card worth sharing. A little clarity on setup, access and where your data goes.

What do I need to install?

For native Codex workers, start with the routing plugin. External ACP routes and the SessionStart hook for loading private instructions are separate, optional additions you can configure when needed.

First-delegation guide
Does every task go to a worker?

No. Delegate when a whole responsibility benefits from its own worker; small or nearly finished tasks can stay with the main agent. Say “solo” or “do not delegate” to keep the work there; corrections normally continue with the same worker.

Controlling delegation
Who chooses models, accounts and access?

You do. Worker Routing supplies no API keys, does not replace the main model and never falls back to a paid route without your authorization. An external ACP route receives the work order through your configured agent; actual access depends on host permissions and sandboxing, not on route configuration alone.

Optional ACP setup
How are main and worker contexts separated?

New native workers do not copy the main conversation. The optional SessionStart hook loads private instructions before the first main-session request, without injecting them into children; host-shared engineering rules may still reach workers. This is an input boundary, not a filesystem sandbox.

Context boundaries
What do completion counts and tokens mean?

Current statistics come from ACP receipts, not native Codex workers. Runtime completion is not engineering acceptance, and observed tokens describe known workload rather than Codex quota savings. Missing usage stays unknown instead of becoming zero.

How the statistics work
What goes into a shared card?

Exports contain aggregate totals, period, timezone and usage coverage, plus the slogan and credit you enter. They do not automatically include work orders, outputs, private route names, paths or internal IDs, and nothing uploads automatically. This website uses synthetic examples and does not connect to your local Dispatch or read receipts.

Sharing and exports