genesis logs
Tail Gateway file logs over RPC (works in remote mode).
Related:
Options
--limit <n>: maximum number of log lines to return (default200)--max-bytes <n>: maximum bytes to read from the log file (default250000)--follow: follow the log stream--interval <ms>: polling interval while following (default1000)--json: emit line-delimited JSON events--plain: plain text output without styled formatting--no-color: disable ANSI colors--local-time: render timestamps in your local timezone
Shared Gateway RPC options
genesis logs also accepts the standard Gateway client flags:
--url <url>: Gateway WebSocket URL--token <token>: Gateway token--timeout <ms>: timeout in ms (default30000)--expect-final: wait for a final response when the Gateway call is agent-backed
When you pass --url, the CLI does not auto-apply config or environment credentials. Include --token explicitly if the target Gateway requires auth.
Examples
genesis logs
genesis logs --follow
genesis logs --follow --interval 2000
genesis logs --limit 500 --max-bytes 500000
genesis logs --json
genesis logs --plain
genesis logs --no-color
genesis logs --limit 500
genesis logs --local-time
genesis logs --follow --local-time
genesis logs --url ws://127.0.0.1:18789 --token "$GENESIS_GATEWAY_TOKEN"
Notes
- Use
--local-timeto render timestamps in your local timezone. - If the local loopback Gateway asks for pairing,
genesis logsfalls back to the configured local log file automatically. Explicit--urltargets do not use this fallback.