agents_Inc
A corporate org chart for AI agents: you ask, the session you talk to dispatches a Lead model, and the Lead runs cheaper Worker models. The aim is more checked work from the AI subscriptions you already pay for.
Table of Contents
- Status & Roadmap
- Why it exists
- Installation
- Quick start
- How it works
- Limitations
- Documentation
- Citation and license
1. Status & Roadmap
Version 0.4.1. The project is experimental and pre-MVP. The governed path (WORKERBEES_GOVERNANCE) is off by default. Changes per release are in the CHANGELOG. The build plan and cut line are in docs/PLAN-MVP.md. Open work is tracked in the issues.
- Now: measure the token cost of delegation against doing the work in one session.
- Next: let a Worker launched by a broker lead its own Workers (#73).
- Later: route work by data classification, so unpublished work reaches only approved providers (#19).
2. Why it exists
Delegated model work can look done while it is wrong. A flat pool of agents has no way to catch that. agents_Inc borrows a corporate org chart. The CEO is you. The CoS (chief of staff) is the session you talk to. A Lead manages one run, and a Worker reports to a Lead.
Cheap models take routine work, and costlier models manage. An author never grades its own work: the Lead checks what its Workers report before anything moves up. Savings are not yet measured, so none are claimed (docs/PLAN-MVP.md).
3. Installation
Requirements: Python 3.10 or later, Bash 3.2 or later, jq, curl, and the Claude Code CLI signed in to an Anthropic subscription. The Codex CLI is optional; when present, it serves the Codex rungs and cross-vendor review.
pip install agents-inc
agents-inc install # skills ship in the package; no checkout needed
agents-inc doctor # first line prints READY when the install works
Restart Claude Code (and Codex, if used) after the install. agents-inc install --without-codex skips Codex on purpose. To install from a git checkout instead, pass --source <checkout>. Optional Gemini, Mistral and OpenRouter keys, the setup decision tree and key storage rules are in docs/START-HERE.md.
Hooks this installs
agents-inc install adds these hooks to ~/.claude/settings.json. It prints the list when it runs.
SessionStart: loads the delegation mandate into each session.PreToolUseonAgent/Task, dispatch-shapedBashandDelegateAgent: adds a routing nudge, warns on duplicate dispatches, blocks persona impersonation, and runs the agent gate.PostToolUseonAgent/Task: marks the dispatch done.UserPromptSubmit: routes@aliasside questions.
Agent gate. Claude's Agent tool skips agents-inc routing, prompt lint, the ledger and verification. The gate decides what happens to those calls.
| Mode | Effect |
|---|---|
advisory (default) |
Nothing is blocked. The session sees a nudge toward agents-inc dispatch. |
enforce |
Blocks every Agent/Task call except foreground Explore, Plan, claude-code-guide and statusline-setup. Background runs are always blocked. |
off |
Same as advisory. Doctor reports it as off. |
- Switch mode:
agents-inc repair --agent-gate enforce|advisory|off. The choice lives in~/.config/agents-inc/settings.json. - One session only: launch with
AGENTS_INC_AGENT_GATE=off claude(orenforce). - Check:
agents-inc doctorprintsagent gate: <mode> (<source>). - Remove every agents-inc hook:
agents-inc unwire. Other hooks stay.agents-inc repairadds them back.
Using agents-inc without the gate.
- Use
Agentonly for read-only, foreground scouts. - Send anything that writes files, runs long, nests or belongs in the ledger through
agents-inc dispatch. - Naming a model chooses the rung, not the route. "Use sonnet" still means
agents-inc dispatch --model sonnet. - Subagents get no SessionStart mandate. If an
Agentprompt may delegate, say in it: sub-delegate only viaagents-inc dispatch. - Verify what an
Agentcall returns yourself, as for any delegate.
4. Quick start
Name your models in plain English. The ladder decides who manages whom, and the rest fills in. You do not hand-pick every model or write JSON.
Write the request to the CoS as <task>. <models>., for example:
"Fix the parser. opus, haiku."
The higher rung manages and the lower rung reports to it, so opus is the Lead and haiku is its Worker. Defaults fill the rest: effort medium, gates derived from the task, and the home repo from the consumer's AGENTS.md. Each extra word, such as an effort level, overrides one default.
| Rung | Claude | Codex | Role |
|---|---|---|---|
| Executive | fable | astra | Final say, irreversible acts, conflicting results |
| Orchestrator | opus | sol | Decompose, dispatch, plan |
| Workhorse | sonnet | terra | Normal coding, research, synthesis |
| Grunt | haiku | luna | Classify, extract, summarize; free Gemini, Mistral and OpenRouter models enter only here |
The CoS then runs one command. It renders the prompt, lints it, snapshots the tree, launches the delegate and checks the report:
agents-inc dispatch --slots slots.json --model sonnet --dry-run # drop --dry-run to launch
agents-inc models chain supervisor=opus # change the default REPORTING CHAIN
Every dispatch prompt carries a REPORTING CHAIN line derived from the ladder, and every launched dispatch writes one dispatched row to the ledger. Codex delegates can write to --cwd by default, the same as a Claude subagent; the slot CODEX_WRITE: no makes one read-only. A worked slots file is in skills/workerbee/slots.md.
Two more entry points need no dispatch. PYTHONPATH=. python3 tools/governance_demo.py --fake, run from a checkout, shows routing, policy checks and ledger records with no provider keys. @haiku <question> inside any Claude Code session sends one side question to a cheaper model before the session model runs (docs/at-route/AT-ROUTE.md).
5. How it works
- Routing. A router picks the vendor and rung for each task from a written policy (agents_inc/routing.json). Rung names are cost classes, not job titles; the reporting chain sets the role.
- Grilling and speckit. The CoS grills you one question at a time until the request is sharp, then a speckit pipeline gates it through spec, plan, tasks and review.
- Verification. A deterministic verifier checks cited claims with no model call. A reviewer from a different vendor then checks the meaning. A Worker's own PASS never decides acceptance.
- Ledger. An append-only JSONL and SQLite ledger records every dispatch, return, review and acceptance decision.
- Models. Each Codex alias is pinned to one slug.
agents-inc modelsreports drift. Model sync promotes new Codex slugs inapproveorautomode and skips pinned aliases.
The full description, including the delegation limits, the 14-element prompt contract, the verification flow and the comparison with other tools, is in docs/HOW-IT-WORKS.md.
6. Limitations
- Cost savings and accuracy against a baseline are not measured. Passing local tests show that the code behaves as written, not that it is reliable in production.
- The governed path is off by default, so a fresh install does not run the enforced cross-vendor review.
- Cross-vendor review catches disagreement between models. It does not catch a blind spot that both vendors share.
- Deterministic checks cover what a script can express, such as a file, a quote or an exit code. They do not replace human judgment on scope or design.
- Free-model capacity varies: a probe on 2026-09-29 found 429 or capacity errors on several free models (docs/BENCH.md). Artifacts stay local; remote publication (Bindle Backend B) is not built.
Updates: new sessions and agents-inc doctor tell you when a newer release is on PyPI (one check a day; AGENTS_INC_NO_UPDATE_CHECK=1 turns it off).
Found a bug or want a feature? agents-inc report bug --title "..." --body "..." (or report feature) prints a draft issue with your version, doctor result and OS; home paths become ~. Add --submit to file it on GitHub with your own gh login.
7. Documentation
| File | Reader |
|---|---|
| docs/START-HERE.md | New users: setup, providers, keys, first job |
| docs/HOW-IT-WORKS.md | Operators and agents: dispatch, verification, comparison, HTTP bridge |
| docs/EXTENDING.md | Adding a vendor, model, task class or domain |
| docs/DECISIONS.md | Binding rulings, with rationale and evidence |
| CONTEXT.md | Glossary: CEO, CoS, Lead, Worker, Mandate, Home repo |
| skills/workerbee/QUICKREF.md | Short form of the dispatch rules |
| docs/RELEASING.md | Release runbook |
8. Citation and license
The DOI for all versions is 10.5281/zenodo.22670100. GitHub's "Cite this repository" button reads CITATION.cff.
agents_Inc is licensed under the PolyForm Small Business License 1.0.0, with one added term that forbids use for AI or machine-learning training. The full terms are in LICENSE.
Metadata
Release files for agents-inc 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agents_inc-0.4.1.tar.gz | 307.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agents_inc-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 661.9 kB
Release files / agents_inc-0.4.1.tar.gz
| Download URL | agents_inc-0.4.1.tar.gz |
|---|---|
| Size | 307.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de69921f7a530c840fe4e267abc0bf9acdf0d686352ad7f6e4efe519d3622b13
|
|
BLAKE2b-256 checksum How to use checksums |
0e05308ad65eb538b4e2d270e0bfddcc7785134b9cbce9af47d50210565499e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / agents_inc-0.4.1-py3-none-any.whl
| Download URL | agents_inc-0.4.1-py3-none-any.whl |
|---|---|
| Size | 354.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6720498ae9d34206311cc1b74b9da8c37e737470cd2d1f7d72f0901fa19a7e6d
|
|
BLAKE2b-256 checksum How to use checksums |
4f78cdd87023c8d0d511b5337a72d4e54ea923ed59a0d5af3e1b75caf47c0e2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for agents-inc 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agents_inc-0.4.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.