Axyome XM

The black box flight recorder for AI-assisted coding.

Axyome XM is a black box flight recorder for AI-assisted coding. Every session is captured as a full forensic trail of the files touched, prompts given, errors hit, commands run and commits made. That gives you traceability from your code back to where it came from: you can see which session changed a file, which assistant (Copilot or Claude Code) made the change, and the prompts behind it. Time Machine replays any past coding day chapter by chapter. Keyword search over your activity and chat history pulls back any moment on demand, and the auto-generated XM Wiki turns your history into a searchable knowledge base.

What is Axyome XM?

• Remembers. The files you edited, the errors you hit, the terminal commands you ran, your commits, and your Copilot and Claude Code sessions. Ask about it in plain words, or replay any past coding day in Time Machine.
• Local. Your activity is recorded and stored on your own machine. No third-party analytics. See Privacy.
• Works with Copilot and Claude Code. Both can recall your history and tell you which assistant changed a file. In Copilot Chat, ask @xm or let Copilot use the memory tools. With your agreement on first run, Claude Code connects to the same memory and gets an agent and three memory skills.

Demo

▶ Watch the 2.5-minute product demo: live product, real data, recorded in VS Code.

"What was that async error I fixed last week?"

Within seconds, your AI assistant retrieves the exact file, error message, and the fix you applied - without you searching through logs or git blame.

-> Full demo walkthrough

Key Features

Install

Search for Axyome XM in the Extensions view (Ctrl+Shift+X) and install it, or run:

code --install-extension axyome-ai.axyome-ai-xm

-> Detailed install guide with platform notes

Quick Start

After installing, Axyome XM activates automatically:

1. Choose what is recorded. A panel lists every source with what it stores; nothing is recorded until you press Start recording ("Recommended" turns them all on).
2. Follow "Get started with Axyome XM" (VS Code's Welcome page, or Welcome: Open Walkthrough...): it checks that Copilot can reach the Axyome XM MCP server and imports your own commits of the last 90 days, so memory has something to recall on day one.
3. Ask Copilot in Agent mode: "What did I work on this week?" The walkthrough's last step opens the chat with the question filled in.
4. Open the Dashboard from the Axyome XM icon in the Activity Bar (or Ctrl+Shift+Alt+M). Axyome: Start Onboarding offers a quick or full tour of the features.

-> Complete onboarding guide

Tutorials

Step-by-step guides that end with something working.

-> All tutorials

Dashboard

8 tabs: Home, Activity, AI, Quality, Intel, Wellness, Replay and System.

-> Dashboard tour with screenshots of every tab

Requirements

Platform Support

Sizes measured on the 1.0.23 build.

MCP Tool Suite

Axyome XM ships with 54 MCP tools (axm_*) served by an embedded MCP server, so GitHub Copilot can use them without manual setup.

Tool diet. To keep every request small, the server lists 11 core tools by default (recall, session summary, context snapshot, error forensics, similar errors, decisions, observations, hybrid search, health and tool discovery). Set axyomeXM.mcp.toolset to all to list all 54. Tools that are not listed still run when called by name, and axm_list_available_tools names what is hidden.

What it writes into your workspace. Nothing without asking. The extension registers its MCP server with VS Code, so Copilot lists Axyome XM without a .vscode/mcp.json in your repository. It then offers to add AGENTS.md, .github/agents/memory.md and recommended VS Code settings (Configure All / Choose... / Skip / Don't Ask Again); skipping or dismissing the prompt writes nothing. Axyome XM: Configure Workspace for AI Memory runs the same setup later.

axm_recall_activity        - Ask what you worked on, changed or ran
axm_get_session_summary    - Summarize what you worked on
axm_find_similar_errors    - Check if you've seen this bug before
axm_search_decisions       - Find out why you chose something
axm_log_decision           - Remember a decision or preference
axm_health                 - Check that your memory is working
... 11 tools by default, all 54 with the setting axyomeXM.mcp.toolset = "all"

-> Full MCP tool reference

Plans

Every feature works on every plan, and a plan never deletes your data — it only changes how much history you can see. Axyome XM runs as a 30-day preview first; after that, a free account is needed to keep using it. Details: app.axyome.ai/pricing.

Privacy

• 100% local storage. On Free and Pro, your activity is stored only on your computer.
• Nothing is recorded until you choose. On first run a panel lists every capture source (Claude Code, Copilot chat and agent edits, files, git, terminal, editor, selections, problems, debug, tasks, coding time) with one line saying what it stores. Recommended turns them all on, every source has its own switch, and nothing is recorded until you press Start recording. Change it any time with Axyome XM: Review Capture Settings.
• No account, no network. Without an account, Axyome XM makes no calls to Axyome servers. There are no third-party analytics, and the built-in MCP server makes no network calls at all.
• Secrets are redacted. Terminal commands, their output and editor selections pass through automatic secret redaction before they are stored.

What is recorded, on your computer only

Before you choose, nothing in this table is recorded.

Secret redaction

Before a terminal command, its output or an editor selection is stored, values matching the redaction patterns are replaced with [REDACTED]. The default patterns cover assignments to names containing api_key, apikey, secret, password, token, credential or auth (for example API_KEY=..., password: ...), bearer tokens, and variables starting aws_, azure_, gcp_, github_ or npm_. Add your own with the axyomeXM.terminalRedactPatterns setting. To stop terminal capture, switch Terminal off in Axyome XM: Review Capture Settings.

Git history import

So that memory has something to recall on day one, a new install with Git on reads your own commits of the last 90 days once, after you choose what is recorded: hash, message, time, branch and per-file line counts. Commits by other authors are left out, and imported commits are not counted as work done with AI. Set axyomeXM.history.gitDays to 0 to skip it, or change the number of days; Axyome XM: Import Git History runs it on demand.

Where your data lives

It holds the database axyome-xm.db (with its journal files). Backups are kept elsewhere, see below.

Where your backups live

Axyome XM keeps its automatic backups outside VS Code's extension storage, so uninstalling or updating the extension never deletes them.

• Open it: run Axyome XM: Open Backup Folder.
• Choose another folder: set axyomeXM.backup.location to a full path (outside VS Code's globalStorage folder), then reload the window. Up to 5 recent backups are kept (axyomeXM.backup.retention).
• Pro: a copy in your cloud folder. You can also keep a copy of each backup in a cloud-synced folder you choose, such as OneDrive, Google Drive, Dropbox or iCloud Drive (axyomeXM.backup.cloudFolder). Your cloud app uploads it; Axyome XM never connects to the cloud provider. Nothing leaves your computer unless you choose a folder.
• Remove them: Axyome XM: Delete All My Data also deletes the backups.

Network

Signed out, Axyome XM makes no calls to Axyome servers. VS Code itself may check the Marketplace for updates; that is VS Code, not Axyome XM.

Your data, your control

• Take a copy: Axyome XM: Export All My Data writes every table to JSON and Markdown in a folder you choose.
• Delete everything: Axyome XM: Delete All My Data (type DELETE to confirm) deletes the database contents, backups and queued events on this computer. Uninstalling the extension removes its database folder, but not the backups, which are kept elsewhere so you can restore; the uninstall and data removal guide lists what is stored and where.
• Clear captured events only: Axyome XM: Clear Captured Events.

Reporting a security issue

Please do not open a public issue for a security problem. Email security@axyome.ai with a description, the steps to reproduce and the impact.

Documentation

Support

• Bug Reports
• Feature Requests
• Questions
• Website

License

Proprietary (c) Axyome - All rights reserved.
See LICENSE for details. Third-party components and their licences are listed in THIRD-PARTY-NOTICES.txt, shipped with the extension.