Supercharge

ACP and daemon

Headless prompts, agent stdio, agent serve, and the inbox daemon

ACP and daemon

Three ways to run the same binary when you are not sitting in the terminal UI.

One shot

supercharge -p "Add a health check and run the unit tests" --yolo
supercharge -p "Explain src/lib.rs" --output-format json

The process exits when the reply is done. Stdout is the answer. See CLI commands for formats and tool filters.

ACP over stdio

Editors and SDKs speak Agent Client Protocol on stdin and stdout:

supercharge agent --always-approve stdio
supercharge agent --always-approve --model your-model-id stdio

Flags that apply to every agent transport go after agent and before the mode name.

FlagMeaning
-m, --modelModel id.
--always-approve, --yoloNo interactive permission prompts.
--agent-profile <PATH>Profile file.
--leader / --no-leaderShare a leader process, or force a local agent.

ACP WebSocket

supercharge agent serve
supercharge agent --always-approve serve --bind 127.0.0.1:2419 --secret TOKEN

Default bind is 127.0.0.1:2419. The secret is --secret or SUPERCHARGE_AGENT_SECRET.

Clients connect to:

ws://127.0.0.1:2419/ws?server-key=TOKEN

A remote CLI:

supercharge --remote ws://127.0.0.1:2419/ws --secret TOKEN

Session state survives a reconnect. This mode is not the HTTP inbox.

Inbox daemon

Clients never launch the CLI. They send HTTP and read server-sent events. The daemon, on the machine that has the files, starts the agent.

supercharge agent daemon --bind 0.0.0.0:6767 --secret TOKEN
InputSource
Bind--bind or SUPERAGENT_BIND. App and Docker hosts use 0.0.0.0:6767.
Secret--secret, else SUPERCHARGE_PASSWORD, else SUPERAGENT_API_TOKEN.

If supercharge-superagent-server is on PATH, the daemon runs that process and you get the full /v1/chat inbox (events, stop, approve, conversations). If that binary is missing, the daemon falls back to ACP WebSocket agent serve.

--leader-socket isolates a local leader. Sockets under ~/.supercharge/leader-*.sock stay visible to supercharge leader list and supercharge leader kill when those subcommands are in your build.

Always-approve is the mode for an unattended daemon. Deny rules still apply.

Ctrl+I
Assistant

How can I help?

Ask me about configuration, installation, or specific features.