CLI
logs
Tail or query the agent logs — Ollama, cloudflared, gateway.
ownllm logs [--follow] [--source <kind>] [--since <window>]The agent supervises three subprocesses and merges their stdout and
stderr into a single log stream stored at ~/.local/state/ownllm/logs/
(or the macOS / Windows equivalent — see Overview).
Common usage
ownllm logs # last 100 merged lines
ownllm logs --follow # tail -f equivalent
ownllm logs --source ollama # only Ollama lines
ownllm logs --source gateway --follow
ownllm logs --since 1h # last hour
ownllm logs --since 15mFlags
| Flag | Description |
|---|---|
--follow | Stream new lines as they arrive. Ctrl+C to exit. |
--source <kind> | One of ollama, cloudflared, gateway. Omit for merged output. |
--since <window> | Relative window like 1h, 30m, 2d. |
Format
Each line is prefixed with the source and a timestamp:
[2026-04-25T10:11:12Z] [ollama] starting server on 127.0.0.1:11434
[2026-04-25T10:11:13Z] [cloudflared] tunnel UP, hostname=acme-agent.ownllm.app
[2026-04-25T10:11:13Z] [gateway] listening on 127.0.0.1:11435
[2026-04-25T10:11:25Z] [gateway] POST /v1/chat/completions user=usr_xxx model=llama-3.3-70b status=200 duration=2400ms in=1230 out=450File rotation
Logs rotate when they reach 50 MB and are kept for 7 days. Old files
are deleted automatically; nothing is uploaded to OwnLLM (audit logs
are a separate, opt-in metadata stream — see
01_TECHNICAL_SPEC.md).
Verbosity
The default log level is info. To get more detail without restarting
the daemon:
ownllm config set log_level debug
ownllm restart gatewayTrace-level logs include request bodies — useful when diagnosing a client-side issue but don't paste them publicly, they include prompts.
Related
doctor— when logs alone don't say what's wrong.status --json— last queue depth, last inference latency, last error.