oly

Supervise CLI sessions with oly

oly skill prints this self-contained guide from the oly binary (no local file read or oly --help is needed). Other embedded skills: oly skill --subagent (multi-agent orchestration), oly skill --daemon (config.json & hot reload), oly skill --apps (web apps).

When to use & prerequisites

• Use oly start when a command is interactive/TUI, may prompt later, must survive terminal disconnects, or needs durable logs/handoff. Run short, non-interactive commands (git, ls, rg, quick tests) directly in the shell.
• Daemon check: Run oly daemon status. Start with oly daemon start --detach only if confirmed stopped. Never stop/restart a shared running daemon. In a sandbox, Access is denied means IPC is blocked while the daemon may still be running — retry the oly command with approval/escalation.

Node federation

Role names describe the remote peer. Verify daemon public identities out of band (oly daemon status, ID-PUB-KEY); never share the private seed.

# On the primary: authorize the secondary's claimed name/key
oly node add worker-1 --role secondary --key 'ed25519 <secondary-base64>'
# On the secondary: name the remote primary locally and claim worker-1 there
oly node add gateway --role primary --url http://primary-host:15443 \
  --key 'ed25519 <primary-base64>' --as worker-1
oly node ls --role primary
oly node info gateway --json

NAME always names the remote locally; --as must match its authorized secondary name on the primary. Primary peers require --url/--as; secondary peers reject them. URLs allow HTTP/HTTPS only, without userinfo/query/fragment. Session --node worker-1 targets a secondary, never an outbound primary.

• oly node ls [--role primary|secondary] [--status connected|connecting|retrying|waiting|disabled] [--json] lists all configured peers. JSON is {items:[...],total:N}.
• oly node info NAME [--json] shows the flat summary: name, role, key, url, as, enabled, status, last_error, next_retry_at.
• Add enables by default; duplicate names fail. Use oly node update NAME [--url URL] [--key KEY] [--as LOCAL_NAME]; role cannot change.
• oly node disable NAME retains configuration and blocks reconnection; enable persists re-enablement. oly node rm NAME deletes configuration/auth and ends federation only, not remote sessions. These changes require operator authorization.
• Mutations require a running daemon and never write state offline. Success means persisted/applied, not connected; inspect ls/info for the observable result.