Runtime Logs

Artuditu records bounded structured diagnostics for long-lived server and display client processes. Logging is local only. Nothing is uploaded.

Read the logs

tail -n 200 ~/.artuditu/logs/server.log
tail -n 200 ~/.artuditu/logs/client.log

The default session stores logs under ~/.artuditu/logs. Named sessions use ~/.artuditu/sessions/<name>/logs. Debug builds and ARTUDITU_HOME overrides retain their normal isolation. artu doctor shows the resolved directory and whether its nearest existing parent is writable.

Each line is one JSON record. server.log and client.log rotate at 3 MiB and keep one archived file, which caps both streams at 12 MiB per session.

Choose a level

The default is info. Set ARTUDITU_LOG before starting the relevant process:

ARTUDITU_LOG=debug artu server restart
ARTUDITU_LOG=off artu server restart

Supported values are debug, info, warn, error, and off. off starts no writer thread and creates no log directory. A running server keeps the level it had at startup, so restart it after changing the variable.

Privacy

Records contain allowlisted lifecycle metadata such as event names, numeric pane IDs, terminal dimensions, safe method names, outcomes, and durations. They do not contain prompts, keystrokes, pane output, scrollback, command arguments, paths, file or DIFF contents, clipboard data, environment variables, native agent session IDs, UHP parameters, responses, or error messages.

Logs are still private runtime data. Review them before attaching them to a public issue.