I have built a supervision and Orchestration layer for Claude Code and other CLI

agentik1 pts2 comments

agentproto CLI — install, run, orchestrate agent CLIs

protocol agentproto.shcli cli.agentproto.shpanel /panel

▍reference host · 9 adapters · v1 on npm<br>Install it. Run an agent. Watch it live.<br>The reference host for AgentProto adapters — run a turn, keep a session, serve a daemon, orchestrate a swarm. One binary.<br>$npm i -g @agentproto/cliCopy

Get startedOpen the panelGitHub

zsh — 60 seconds to a supervised agent<br>$ npm i -g @agentproto/cli<br>+ @agentproto/cli — 9 adapters detected<br>$ agentproto serve<br>● gateway up · http://127.0.0.1:18790 · panel ready<br>$ agentproto sessions start claude-code --prompt "fix tests"<br>● s_7f2k · claude-code · running — watch it in the panel

the panel<br>Every session, live, in one dashboard<br>Session sidebar, terminal/chat/JSON/event views per session, shareable deep-links over a tunnel. It talks to whatever daemon it finds on ports 18790–18795, local or remote.

Open the panel<br>panel · connected · http://127.0.0.1:18790

agentproto runRun an agent locally<br>Install an adapter (claude-code, hermes, …) and run a single turn or a persistent session.<br>agentproto serveShare with a hosted agent<br>Log in via device flow, then expose your machine as a daemon over an outbound WebSocket tunnel.<br>agentproto run-swarmOrchestrate a swarm<br>Compose a substrate + dispatcher + participants in a manifest. Kernel-routed, plugin-extensible.<br>agentproto mcp-bridgePlug into Claude Code<br>The daemon is an MCP server — HTTP transport for Claude Code, bundled stdio bridge for Codex, Cursor, Claude Desktop.

reference docs<br>Verb-by-verb usage, concepts, and exact on-disk schemas — synced from the package's own docs at build time.

Browse the docs →

agentproto claude code panel agent session

Related Articles