Adopting AgentsMesh in an Existing Project

If your project already has AI tool configs scattered across .claude/, .cursor/, .cline/, and so on, this guide walks you through consolidating them under AgentsMesh without losing any existing config.

Prerequisites

AgentsMesh installed — pick any method from the installation guide: Homebrew, standalone binary, or npm install -D agentsmesh for Node.js projects.
The project already has tool configs in one or more tool directories.

Migration steps

Initialize the canonical directory
Terminal window
```
agentsmesh init
```
AgentsMesh scans the project and prompts you to import each detected config. Use --yes to import everything without prompts:
Terminal window
```
agentsmesh init --yes
```
Starter example files are added only for canonical folders that stay empty after import (so imported commands or skills are not duplicated with example stubs).

Verify the canonical files

After import, review what was created:

ls .agentsmesh/rules/
ls .agentsmesh/commands/
ls .agentsmesh/agents/
ls .agentsmesh/skills/
cat .agentsmesh/mcp.json
cat .agentsmesh/permissions.yaml
cat .agentsmesh/hooks.yaml

Check that all your rules, commands, agents, and other config came through correctly.

Configure agentsmesh.yaml

Set the targets your team actually uses:

version: 1
targets:
  - claude-code
  - cursor
  # add others as needed
features:
  - rules
  - commands
  - agents
  - skills
  - mcp
  - hooks
  - ignore
  - permissions

Regenerate for all targets
Terminal window
```
agentsmesh generate
```
This writes fresh output to each tool directory based on the canonical sources.
Verify nothing unexpected changed
Terminal window
```
agentsmesh diff
```
The diff should show no changes (since the generated output should match what was imported). If there are differences, review them — they represent normalization that AgentsMesh applied during the round-trip.

Commit everything

git add .agentsmesh/ agentsmesh.yaml .claude/ .cursor/
git commit -m "feat: adopt agentsmesh for AI tool config sync"

What to tell your team

Edit .agentsmesh/ files (not tool directories directly)
Run agentsmesh generate after editing
Commit both .agentsmesh/ and the generated tool directories
CI will run agentsmesh check to catch drift

Adding more tools later

When a new developer joins who uses a different tool (e.g., Gemini CLI), add it to agentsmesh.yaml and generate:

targets:
  - claude-code
  - cursor
  - gemini-cli   # new addition

agentsmesh generate

Their tool directory (.gemini/) is now in sync with the rest of the team.