How Syncing Works

On Install

When you install Altitude, agents sync automatically on the next console command if .claude/agents doesn't exist yet. This ensures you get agents immediately without needing to run a separate command.

On Boost Updates

When boost:install or boost:update runs, Altitude syncs with --force, updating all agents to the latest versions.

File Conflicts

Altitude agents use common names like architect, database, and livewire. If you have custom agents with the same names, they will be overwritten on boost updates.

To keep custom agents, use different names:

.claude/agents/
├── architect.md        # Altitude (will be updated)
├── my-architect.md     # Your custom version (safe)
└── project-rules.md    # Your custom agent (safe)

Alternatively, disable auto-sync and manage updates manually:

ALTITUDE_AUTO_SYNC=false

Why Altitude?

AI assistants need context about your stack to give good advice. But documentation changes between versions, and copy-pasting docs into prompts wastes tokens and goes stale.

Altitude solves this by:

• Separating concerns — Agents handle decisions and workflow, Boost handles docs
• Package-aware publishing — Only get agents for packages you actually use
• Workflow commands — Common tasks like /ship, /test, /debug work out of the box
• Never stale — Agents reference mcp__laravel-boost__search-docs instea...