Archon
The control room for your AI agent fleet.
Most agent tooling only watches. Archon also gives you the controls — kill switches, start/stop, restart — so when an agent or automation goes wrong, you can actually stop it. One live pane for everything your agents are doing, plus a control API to act on it.
Why Archon
Running several agents (OpenClaw, Claude Code, CrewAI) plus automations (Make/n8n) means events scattered across a dozen logs. Archon normalizes them into a single event stream, streams it live to one dashboard, and — critically — lets you act: hit a kill switch, restart a service, stop an automation.
- See — every agent session, automation, and service in one live feed
- Control — kill switches, start/stop/restart, pre-configured and safe
- Alert — Telegram/webhook on failures and state changes
- Zero dependencies — a stdlib Python server + one HTML file
Quick start
git clone https://github.com/archonhq/archon && cd archon
pip install .
archon serve --sessions-dir ~/.openclaw-autoclaw/agents/main/sessions \
--control-config examples/control-config.json
# open http://127.0.0.1:8000
How it works
framework logs ──► adapter ──► event stream ──► dashboard (HTTP/SSE)
▲
control API
│
framework APIs ◄─────── executor ◄──┘
Adapters translate framework-specific logs into one JSON event stream (see the telemetry contract). The dashboard and control API consume only that contract — a new framework is one adapter away.
Control is safe by design. Commands are pre-configured in a config file,
never supplied by the client. The control API accepts only {action, target}
and routes it to a matching command — client input never reaches the shell
unbounded. See examples/control-config.json.
Adapters: OpenClaw (reference) · Make.com · trading monitor · Claude Code (planned) · CrewAI (planned) · n8n (planned) · generic webhook (planned)
Status
Pre-alpha. Reference implementation: OpenClaw adapter. The control plane is proven in production on a live trading-monitor deployment (kill switch, risk rails, Telegram alerts, VPS health).
Roadmap
| Phase | Scope |
|---|---|
| 0 | Telemetry contract, adapters, auth, packaging, landing page |
| 1 | 10–20 self-host users, iterate |
| 2 | Hosted tier (ingest API, multi-tenant, billing) |
| 3 | Trading edition (executor, kill switch, pager) |
License
MIT
Metadata
Release files for archon-hq 0.1.0
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 | |
|---|---|---|---|---|
| archon_hq-0.1.0.tar.gz | 18.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| archon_hq-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.1 kB
Release files / archon_hq-0.1.0.tar.gz
| Download URL | archon_hq-0.1.0.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b10e0524676c2e6e854b90a36bf5d157a4c3be717c0130a30f1b30b12b64e5d3
|
|
BLAKE2b-256 checksum How to use checksums |
28338f1f4c0ba413f3dbdb23fa995a903dcf539d516e7d3f24f364419b933f24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.1
|
Release files / archon_hq-0.1.0-py3-none-any.whl
| Download URL | archon_hq-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6500b35768e881503e5c748bbd689c948b322eb20cb6ae5a54dec5d07cbf3e5
|
|
BLAKE2b-256 checksum How to use checksums |
1c80f8559512aff84318fe7de9e72486eaa46ea83cc239d59fec2f5187a82813
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.1
|
Security for archon-hq 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.