Axon Fleet brings the local Axon runtime into Visual Studio Code. It gives you a live view of running agents alongside the workspace they belong to, with focused resource views for inspecting an agent while you work.
What it provides
The Blueprints view is one tree rooted on your agent projects. Each row is the agent's project folder: expand it and you get that folder's real contents, the source tree you already know, plus two synthetic folders below them:
- instances/ — live local Axon processes for that agent, with their PID, session, and cognet lens. Subagents nest under the instance that spawned them.
- sessions/ — recent completed runs, replayed through the same Logs, Events, Trace, and Engine panes as a live instance.
Navigation is native: clicking a row expands it, exactly like the Explorer. To inspect something in the Axon Console, use the inspect button that appears on the row when you hover it.
Agents running from a folder outside your workspace appear under Elsewhere, so nothing running on the machine is ever hidden.
The extension observes only the local Axon runtime. It does not upload your workspace or require an Axon account.
Getting started
- Install the extension.
- Open a workspace containing one or more Axon agents (any folder with an
axon.config.ts, including the workspace root itself). - Open the Axon Fleet icon in the Activity Bar.
- Select a project, instance, or past session to inspect it. Use Axon: Open Console from the Command Palette to open the runtime panel.
Agent projects are discovered from disk, so the tree is populated before you run
anything. Start an agent with axon dev and it appears under that project's
Instances group.
Requirements
- Visual Studio Code 1.95 or newer.
- Axon installed locally for runtime instance discovery.
Feedback
Report issues at the Axon repository.
Development
bun run release:package
release:package type-checks, builds, and writes a Marketplace-ready VSIX to
artifacts/axon.vsix.
Use bun run build to additionally install that artifact into the local code
command.
Releasing
Fleet ships through the repo's release gate, never by hand:
bun run libs/repo/bin/arc.ts ship fleet # gate, then publish
bun run libs/repo/bin/arc.ts ship fleet -v # gate only, publish nothing
The gate runs libs/cloud and libs/axon/platform — typecheck and suites for
both — before fleet's own typecheck, because the extension's RPC bridge marshals
Platform() calls directly and libs/cloud is what it authenticates through. A
break in either reaches users as a broken extension.
The final deploy step bumps the patch version, builds the VSIX, and publishes
it. The bump happens first, deliberately: Marketplace versions are immutable
and cannot be reused after unpublish, so the number built into the artifact has
to be the one that ships. Publishing needs a PAT — ~/.vsce from vsce login arclabs, or VSCE_PAT in the environment.