Command log

Updated on November 10, 2026

Every action of a CLI machine leaves a trace in its log: activation, host list, run, snippet, MCP tool, confirmation, rotation, sign out, revocation. It can be read in Settings › CLI machines, by opening the machine, and on https://app.konsolity.com/cli-machines.

Start and end

For a run, the CLI writes a line before starting the command, then a second one at the end, with the exit code and the duration. If writing the start fails (network down, server unreachable), the command is not run: nothing runs without a trace.

The server itself writes the events that concern it: activation, token rotation, revocation, confirmations, scope refusals.

Content of a line

  • When: the date and time;
  • Which tool: hosts, run, snippet, sessions, mcp:<tool>, serve:<tool>, login, rotate, logout;
  • Which host: its label;
  • Which command: its text, limited to 4,000 characters;
  • Decision: allowed (with the rule that allowed it), denied, confirmed or refused at confirmation;
  • Exit code and duration of the run;
  • the CLI session and, where relevant, the confirmation request.

What the log does not contain

Never the output of the command. Never a password, a key, a token or a machine key.

Retention

Lines are encrypted at rest and kept for 90 days, then deleted. Revoking a machine does not delete its log: it stays available until the end of the 90 days.

Filters

Filter by machine (on the machines page), by period (from, to) and by decision (allowed, denied, confirmed, not confirmed): the most recent lines show first and “Older lines” loads the rest. The export uses the same filters.

Export

Export produces a CSV file (spreadsheet, English headers) or a JSON file (tools, archiving) for the chosen period. Keep a monthly export if you need a trace beyond 90 days.

Good practices

  • Go through the log after widening a scope: refusals show what was attempted.
  • A repeated refusal of a legitimate command points to a rule to add; an unexpected refusal, to a request to look into.
  • A start line without an end line marks an interrupted command (revocation, end of session, outage).