Skip to content
| Marketplace
Sign in
Visual Studio Code>Debuggers>Axon FleetNew to Visual Studio Code? Get it now.
Axon Fleet

Axon Fleet

arclabs

|
9 installs
| (0) | Free
Debug Axon agents in VS Code — live processes, session history, flame graphs, and the exact prompt sent to the model.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Axon Fleet

See what your agents are actually doing.

Axon Fleet puts the local Axon runtime in your editor: every agent you have, every process running right now, every conversation on disk — and a debugger that shows you exactly what the model was sent and what it did with it.

An Axon instance selected, with its event log open in the console


Three drawers: source, live, history

Everything is one click. No nesting, no folders to expand first.

Agents — every agent project on your machine, with its version and whether it is running. Start a dev server from the row.

The Agents drawer listing agent projects with versions

Instances — every agent process alive right now, with uptime. Subagents nest under the instance that spawned them, because that is real containment — nothing else nests.

Sessions — every conversation on disk, searchable by name, agent or id. Name a session in the terminal with :session rename and it is findable here forever.

The Sessions drawer with a search box and named sessions

A finished session opens exactly like a live instance — same panes, same tabs. That is the point: debugging a run that ended is the same act as watching one that has not.

The debugger

Selecting anything opens the Axon Console with six views over that run.

Events — the full structured log: every module setup, every capsule attach, every tool call and its result, timestamped and filterable. This is the session's .jsonl, rendered.

The event log showing module setup and boot events with payloads

Trace — the same run laid against time as a flame graph. Where the seconds went, which kernel run owned them, and what nested inside what.

A flame graph of a run beside the live terminal

Engine — what was actually sent to the model. Not a summary: the assembled prompt, split into Meta, Scope, System, Contract and Timeline, with the raw completion beneath it.

The engine pane showing the assembled tool scope sent to the model

When an agent does something you did not expect, the answer is usually not in what it said — it is in what it was given. This is the pane that shows you.

Logs, I/O and Capsule cover process output, the sensory timeline, and what ran inside the sandbox.

Registry

Browse and install agents, modules, cognets and extensions from the Axon registry without leaving the editor.

The Axon registry browser in the sidebar

Works with the terminal

Fleet is the editor half of Axon, not a replacement for it. The Axon TUI can drive this window — :open log, :open flame, :open engine from a conversation put that pane in front of you, pointed at the run you are having.

It goes the other way too: Open in TUI on any instance jumps your terminal to that conversation.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft