CAMI Documentation

Understanding Your Workspace

As you work with CAMI, you'll notice files appearing in your workspace and projects. Here's what they are and why they matter.

Your CAMI Workspace

Everything CAMI needs lives in ~/cami-workspace/:

typescript
~/cami-workspace/
├── config.yaml              # Your sources configuration
├── deployments.yaml         # Tracks where agents are deployed
├── .mcp.json                # MCP server configuration
├── CLAUDE.md                # Workspace documentation
└── sources/                 # Agent collections
    ├── official-agents/     # From Lando Labs
    ├── team-agents/         # Your team's agents
    └── my-agents/           # Your personal agents

Key Files Explained

config.yaml - Your Agent Sources

Lists where CAMI finds agents. Created when you add sources:

yaml
# "Add the official CAMI agents source"
agent_sources:
  - name: official-agents
    type: local
    path: ~/cami-workspace/sources/official-agents
    priority: 100
    git:
      enabled: true
      remote: git@github.com:lando-labs/official-agents.git
  - name: my-agents
    type: local
    path: ~/cami-workspace/sources/my-agents
    priority: 10

Priority: Lower number wins. Your agents (10) override official agents (100).

See Agent Guilds for ready-to-use agent collections you can add.

deployments.yaml - Central Tracking

Tracks all your agent deployments across projects:

yaml
# Updated automatically when you deploy agents
version: "1"
deploy_locations:
  - name: my-web-app
    path: /Users/you/projects/my-web-app
    agents:
      - name: frontend
        source: official-agents
        version: "1.1.0"
      - name: backend
        source: official-agents
        version: "2.0.0"

CAMI uses this to answer "Which projects need agent updates?"

Files in Your Projects

When you deploy agents, CAMI creates files in your project:

typescript
your-project/
├── src/
├── .claude/
│   ├── agents/              # Your deployed agents
│   │   ├── frontend.md
│   │   └── backend.md
│   └── cami-manifest.yaml   # What's deployed here
└── CLAUDE.md                # Project documentation

cami-manifest.yaml - Project Manifest

Tracks exactly what's deployed in this project:

yaml
# "Deploy frontend and backend to this project"
version: "1"
agents:
  - name: frontend
    version: "1.1.0"
    source: official-agents
    hash: sha256:a1b2c3...
    deployed_at: "2025-11-23T10:30:00Z"
  - name: backend
    version: "2.0.0"
    source: official-agents
    hash: sha256:d4e5f6...
    deployed_at: "2025-11-23T10:30:15Z"

The hash lets CAMI detect when updates are available.

Optional Configuration Files

STRATEGIES.yaml - Tech Stack Guidance

Tell agents about your project's technology choices:

yaml
# "My project uses React 19 with TypeScript and Tailwind"
stack:
  frontend:
    framework: react
    version: "19"
    language: typescript
    styling: tailwind
  backend:
    runtime: node
    version: "20"
    framework: express
conventions:
  testing: vitest
  formatting: prettier

Agents read this to give advice matching your stack. Place in your project root or .claude/.

.camiignore - Skip Files

Tell CAMI to ignore certain files or directories:

typescript
# "Ignore the legacy folder and vendor files"
legacy/
vendor/
*.generated.js
node_modules/

Uses the same patterns as .gitignore.

You Don't Create These Manually

All these files are created and updated through conversation with Claude:

typescript
"Add the official agents source"        → config.yaml updated
"Deploy frontend to my project"         → manifest created, agents copied
"My project uses React 19 and Node 20"  → STRATEGIES.yaml created
"Ignore the legacy folder"              → .camiignore created

CAMI handles the file management. You just describe what you need.

When Things Go Wrong

If CAMI seems confused about your workspace:

typescript
"Can you check my CAMI configuration?"
"What sources do I have configured?"
"What agents are deployed in this project?"
"Normalize this project"  # Fixes inconsistencies

CAMI can diagnose and fix most issues through conversation.

Next Steps