claude-org-runtime
Python runtime extracted from claude-org-ja for Claude Code orchestrator setups using renga panes. Sibling of core-harness; provides a dispatcher runner, state schema, and reference role prompts (secretary / dispatcher / curator).
Not an AI agent framework — this is plumbing for human-driven Claude Code orchestrator workflows, not an autonomous-agent toolkit.
Status
0.1.0: dispatcher runner + settings generator + reference role
prompts + state schema + v1->v2 polymorphic migrate. This is the first
release that consumers (notably claude-org-ja) can pip install to
replace their in-tree tools/dispatcher_runner.py /
tools/generate_worker_settings.py / tools/role_configs_schema.json.
Install
pip install claude-org-runtime==0.1.0
For local development:
git clone https://github.com/suisya-systems/claude-org-runtime
cd claude-org-runtime
python -m pip install -e .[dev]
Quick start
The single-command front door brings up a whole orchestrator session:
# Start the broker daemon, mint a secretary token, write its mcp-config,
# and drop you into an interactive Claude Code TUI — one command:
claude-org-runtime org up
# Tear it back down: close residual broker panes, request a signal-free
# shutdown, verify it stopped, and clean up the sidecar:
claude-org-runtime org down
org up is reuse-or-start: a reachable daemon is reused, a stale sidecar
is replaced. The lower-level building blocks are still available directly:
# Render a per-role settings.local.json:
claude-org-runtime settings generate \
--role default \
--worker-dir /path/to/worker \
--claude-org-path /path/to/claude-org \
--out /path/to/worker/.claude/settings.local.json
# Compute a Dispatcher delegation action plan:
claude-org-runtime dispatcher delegate-plan \
--task-json .state/dispatcher/inbox/<task_id>.json \
--panes-json panes.json \
--state-dir .state
See docs/cli.md for the full CLI reference, the org up /
org down flags, and the migration recipe for claude-org-ja consumers.
dispatcher spawn-prompt-step --target <pane> also writes a decision record
under <state-dir>/dispatcher/spawn-prompt/ for a send_keys guard hook; its
format is a stable contract documented in
docs/cli.md.
Broker
The broker is a renga-free transport for orchestrator sessions: a localhost
MCP daemon plus a persisted queue and a terminal adapter (tmux / wezterm /
herdr backends; herdr is opt-in and POSIX / WSL-only, not supported on
native Windows). Agents talk to it over plain HTTP MCP instead of a renga tab, so
a session can run without the renga UI. It is billing-neutral by design —
it only ever launches the interactive Claude Code TUI through a builder
that rejects headless flags. org up / org down are a thin launcher over
this control plane (the daemon.json sidecar + admin RPC); see
docs/cli.md for details.
herdr version requirement: the herdr backend supports herdr 0.7.5
(wire protocol 17) and herdr 0.9.0-0.9.3 (protocol 22). herdr 0.9.x needs a
claude-org-runtime release newer than 0.1.49. herdr 0.7.0-0.7.4 (protocol
14 / 16) and herdr 0.8.x (protocol 19 / 20) are not supported; runtime 0.1.49
and older still accept 14 / 16. An unsupported protocol is rejected at startup
with herdr_protocol_unsupported rather than failing silently.
claude_org_runtime.terminal.herdr.protocol_for_version((major, minor, patch))
maps a herdr release to its wire protocol (None for releases it does not know).
Reference role prompts
The runtime ships English reference prompts for the three roles used in
the claude-org-ja reference organization (secretary, dispatcher,
curator):
from claude_org_runtime.prompts import load, load_meta
prompt = load("dispatcher") # raw markdown, frontmatter included
meta = load_meta("dispatcher") # {'role': 'dispatcher', 'source': ..., 'status': ...}
These are reference, not prescriptive. They capture one working
configuration from claude-org-ja, not an "agent framework" opinion.
Consumers are expected to load them as a starting point and then override
or rewrite sections from their own project-root CLAUDE.md (or skill
files) to match their organization's conventions, terminology, and slash
commands.
Related
- core-harness — sibling repo with reusable safety primitives for Claude Code harnesses.
- claude-org-ja#129 — tracking issue for the extraction effort that produced this runtime.
- Issues for this repo.
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for claude-org-runtime 0.1.50
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 | |
|---|---|---|---|---|
| claude_org_runtime-0.1.50.tar.gz | 471.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| claude_org_runtime-0.1.50-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 881.6 kB
Release files / claude_org_runtime-0.1.50.tar.gz
| Download URL | claude_org_runtime-0.1.50.tar.gz |
|---|---|
| Size | 471.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9cb2cf5c231fab0f11e4dedd3d7cb97dd2736984b11914e4f29d50a286f47d1f
|
|
BLAKE2b-256 checksum How to use checksums |
4b864d994a86783eee3303f130f790ad59e76e4458430d8bc26f51be85588323
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 12, 2026.
Transparency logRelease files / claude_org_runtime-0.1.50-py3-none-any.whl
| Download URL | claude_org_runtime-0.1.50-py3-none-any.whl |
|---|---|
| Size | 410.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f0e7f49e406609fffb3545a697b30a53f1f53b565c2cce5dc6baa14f77909a6a
|
|
BLAKE2b-256 checksum How to use checksums |
2c64582e8da652556d4ca2a6d619861bc313f68e4e8834573250021ba1bf9bbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 12, 2026.
Transparency logSecurity for claude-org-runtime 0.1.50
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 claude_org_runtime-0.1.50.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 12, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
