axMap

Several AI agents. One repository. Clear ownership before every edit.

axMap is a collaboration CLI that claims files and folders before work begins and rejects overlapping claims. Codex, Antigravity and Claude Code can use claims, releases, status and messaging through MCP.

English · 한국어   /   Node.js 20+ · Git · MIT

Install

npm install -g axmap-cli@latest
axmap setup

Run setup once from any folder, then restart your AI tool. Each Git repository's ledger is prepared on first use. Collaborators must share the same remote ledger.

Usage · MCP setup · Development

Changelog

Newest changes first.

1.4.0

October 20, 2026

Codex and Antigravity can exchange tasks automatically, with measured token usage and bounded conversations.

Added

• axmap bridge serve codex|agy explicitly starts persistent managed CLI sessions. bridge chat relays short messages until completion or a configured limit.
• MCP ax_chat, ax_dialogue, and ax_chat_stop start, inspect, and stop automatic relay. Per-request and cumulative token counts include cache details; idle waiting makes no model calls.
• The separate prototype axmap run command connects a user-launched interactive terminal.
• The terminal dependency ships with npm installation and is copied into setup's installed runtime.

Removed

• Code visualization screens, the Electron app, analysis and corpus tools, and their tests and research documents.
• Setup and MCP now share CLI discovery from a dedicated source module.

Validation

On Windows, actual Codex 0.163.0 and agy 1.4.2 completed a four-turn automatic exchange with retained context, followed by a two-turn MCP background exchange. These six model turns processed 102,590 tokens, including 54,400 cached input tokens and 393 output tokens. CLI context dominates short-message costs; budgets are checked before the next turn, not enforced as a hard limit within an active turn. The separate interactive PTY prototype remains validated with simulated programs only. Read the development status →

1.3.3

October 16, 2026

Windows setup connects npm-installed Codex correctly.

Fixed

• axmap setup launches the Codex package's Node entry directly.
• Paths containing spaces and quoted arguments reach Codex without shell reinterpretation.

Release source →

1.3.2

October 16, 2026

Choose your messaging name. Discover teammates automatically.

Added

• Interactive setup asks for a display name. Change it with axmap setup --name "Your name".
• First use in a repository shares its Git email and your display name through the team's user ledger.
• axmap bus contacts lists known recipients.

Updated

• Messages sent to a known name are addressed by email, preserving delivery and read history after name changes.
• Duplicate names require an email address. Failed profile updates are reported and retried on later use.
• Git identity settings and voting permissions remain unchanged.

Release source →

1.3.1

October 15, 2026

One setup, from any folder.

Updated

• Installation and MCP registration work outside Git repositories.
• Running setup in a folder does not pin future work to that repository.
• Registration refreshes server paths and environment settings while preserving personal settings and other servers.

Use axmap setup --repo <path> to prepare a specific repository's ledger and commit hook.

Release source →

1.3.0

October 15, 2026

Your session follows its working repository.

Added

• Status and claim commands prepare missing ledgers automatically, removing the repeated init step.
• MCP follows client workspace roots and their change notifications.

Updated

• Existing remote ledgers are reused, and linked worktrees share one ledger.
• Sessions in separate repositories keep independent targets.
• A remote access failure is never treated as an empty ledger.

Use the MCP tool's cwd argument when roots are unavailable or the target is ambiguous. Run axmap hook install in repositories that need commit enforcement.

Release source →

Installation & upgrades · Protocol · Report an issue · MIT license