How many repos can one workspace include?

Designed for typical monorepo and multi-root IDE layouts; practical limits depend on machine resources and context strategy.

Do repos share one safety policy?

Workspace-level rules can combine with per-repo rules; stricter policy wins on conflict.

Does Cursor multi-root work?

Yes — point axme_context at the correct repo path per task; see /integrations/cursor/.

AXME CODE

Work across multiple repositories in one coding agent session

Real engineering work spans repos. Claude Code has one repo in context at a time, making cross-repo refactors, API contract updates, and shared-library changes painful.

AXME Code maintains context across multiple repositories simultaneously — useful for microservice refactors, monorepo splits, and cross-repo dependency updates.

Start free Read docs

Real engineering work spans repos. Claude Code has one repo in context at a time, making cross-repo refactors and API contract updates painful.

Workspaces that match real engineering

Products span API repos, frontends, infra, and contracts. Single-repo context forces sequential clones and lost links between changes.

AXME Code supports per-repo .axme-code/ directories with merged workspace context — decisions and memories can reference cross-repo impact, and setup detects monorepo layouts (Nx, pnpm workspaces, submodules, and more).

CAPABILITIES

How it works.

Multi-repo context

Several repos in one session.

Setup

Declare repo graph and roots.

Cross-repo decisions

Log changes spanning services.

Conflict detection

Flag incompatible changes.

Setup and conventions

Run axme-code setup in each repo or at the workspace root per MULTI_CLIENT.md guidance. Declare which repos participate in a feature so handoff lists touch points across services.

Record cross-repo decisions explicitly — e.g. API contract version in repo A must ship before client change in repo B — so agents do not optimize locally and break the system.

Common questions

How many repos can one workspace include?: Designed for typical monorepo and multi-root IDE layouts; practical limits depend on machine resources and context strategy.
Do repos share one safety policy?: Workspace-level rules can combine with per-repo rules; stricter policy wins on conflict.
Does Cursor multi-root work?: Yes — point axme_context at the correct repo path per task; see /integrations/cursor/.

Ship your first durable agent — in under 10 minutes.

Free tier. No credit card. Self-host or hosted — your choice.

Start free now Read the docs