Running zerocode
Local setup
On the same machine as the daemon, no extra configuration is needed:
sh
zerocode
zerocode finds the daemon’s local endpoint automatically: <data_dir>/data/daemon.sock
on Unix, \\.\pipe\zeroclaw-<hash> on Windows. If the daemon isn’t running,
zerocode spawns an ephemeral one.
Switching sessions
In the Chat and Code panes you can load or switch existing sessions without restarting zerocode:
- Switch session opens the session list (default chord: Ctrl+S; rebindable in the keymap).
- Use the list-navigation keys to move the selection (defaults: Up/Down).
- Enter switches to the highlighted session.
- New session starts fresh (default chord: Ctrl+N; rebindable).
The in-app help overlay shows your live key bindings for these actions.
Chat/Code sessions and ACP-backed sessions use different stores. If you use the ACP protocol directly, use session/load when you need transcript replay and session/resume when you only need the server-side session state restored. See the ACP documentation for protocol-level details.
CLI flags
| Flag | Description |
|---|---|
--connect <url> | Connect to a remote daemon via WSS (e.g. wss://host:9781) |
--tls-skip-verify | Skip TLS certificate verification. Required for self-signed certs |
--config-dir <path> | Override the config directory |