The Console

A session is a .jsonl file — every request, every engine call, every command, every policy decision, in one order. Everything you need is already on disk. Reading it by hand is the problem.

The Axon Console is that file, rendered.

Four panes

Logs — what it said while running.

Events — what happened, in order.

Trace — where the time went.

Engine — what the model actually saw.

Trace & Events find where a run went wrong. Engine finds why.

Live and finished are the same interface

Every pane reads from a source: a running instance, or a session file on disk.

Watch a run happen:

Or open one that finished last week and read it through the identical panes:

A finished session is not a lesser view. It is the same file the live view was tailing, which stopped appending. A run you missed is as debuggable as one you are watching.

Three things to point it at

An instance tails live. A session replays. An agent is the stable subject — its Sessions tab lists every past run, so you pick one and inspect it without re-targeting the console.

It works for any agent

The panes read kernel:* telemetry — the runtime's own meter around every engine call, tool, and command. Nothing from inside a cognet.

So a custom cognet gets the same Trace and the same Engine view as a stock one, and never needs to know a debugger exists.

Next: The Engine Pane — the one view you cannot get any other way.