logs and flush
Read, follow and filter an app's logs, and truncate them.
logs
oxidepm logs api # the last 15 lines
oxidepm logs api -f # follow
oxidepm logs api --lines 100
oxidepm logs api --err # only stderr
oxidepm logs api --grep "timeout|refused"| Option | Meaning |
|---|---|
-f, --follow | Follow the output. |
--lines <n> | How many lines to show. 15 by default. |
--out, --err | Only stdout, or only stderr. |
--grep <regex> | Only lines that match the pattern. |
$ oxidepm status ╭────┬────────┬──────┬─────┬───┬─────────┬──────┬─────┬────────╮ │ id │ name │ mode │ pid │ ↺ │ status │ cpu │ mem │ uptime │ ├────┼────────┼──────┼─────┼───┼─────────┼──────┼─────┼────────┤ │ 1 │ mailer │ cmd │ - │ 3 │ errored │ 0.0% │ 0B │ 0s │ ╰────┴────────┴──────┴─────┴───┴─────────┴──────┴─────┴────────╯ $ oxidepm logs mailer --lines 3 [2026-10-31 04:11:47.153] cannot reach smtp [2026-10-31 04:11:47.559] cannot reach smtp [2026-10-31 04:11:48.362] cannot reach smtp
flush
oxidepm flush apiflush truncates the active log files of an app. Rotated files stay. The log contents are lost, so read them first. Log rotation is automatic (Log files), so flushing to save space is rarely needed. flush is a dangerous request: an AI actor cannot make it.