Agent Pull

Use camber agent pull when you want to bring a mirrored Camber agent back to your local machine.

The command restores the agent’s Mirror Context into a local project folder and installs the agent and skills for a supported local assistant.

Basic usage

camber agent pull @owner.alias

By default, this uses the Claude Code integration and writes into the current directory.

You can choose the local assistant integration:

camber agent pull @owner.alias --integrate claude-code
camber agent pull @owner.alias --integrate cursor

You can also choose the parent destination:

camber agent pull @owner.alias --dest /path/to/local/folder

What gets created

The command creates one project folder under the destination:

project_<owner>_<alias>/
├── .claude/ or .cursor/
├── README.md
├── chat/
├── knowledge-base/
├── project/
├── requirements/
├── schema/
└── instruction.md

For example:

camber agent pull @nhantran.context-mirror-demo

creates:

project_nhantran_context_mirror_demo/

The pulled mirror files are copied from:

stash://<owner>/.camber/agent-context/<agent-alias>/

Camber restores all files and folders stored in that mirror root. The folders shown above are the standard Mirror Context layout, but extra folders added to the mirror are pulled too.

Claude Code integration

With --integrate claude-code, Camber writes the local agent file to:

project_<owner>_<alias>/.claude/agents/<owner>.<agent-alias>.md

Skills are restored to:

project_<owner>_<alias>/.claude/skills/<skill-name>/

Cursor integration

With --integrate cursor, Camber writes the local Cursor rule to:

project_<owner>_<alias>/.cursor/rules/camber-agent-<owner>.<agent-alias>.mdc

Skills are restored to:

project_<owner>_<alias>/.cursor/skills/<skill-name>/

Skill behavior

Cloud skill folders are not restored as a root skills/ folder.

Instead, Camber remaps each skill into the selected local assistant’s skill folder:

• Claude Code: .claude/skills/<skill-name>/
• Cursor: .cursor/skills/<skill-name>/

Each skill folder keeps its SKILL.md, scripts, references, assets, and nested files.

Replace behavior

camber agent pull replaces the generated project_<owner>_<alias>/ folder each time it runs.

Use this when you want the local copy to match the latest state held by the Camber agent.

JSON output

Use --output json when scripting:

camber agent pull @owner.alias --integrate claude-code --output json

Example response:

{
  "agent": "@owner.alias",
  "integration": "claude-code",
  "dest": "/path/to/project_owner_alias",
  "agent_file": "/path/to/project_owner_alias/.claude/agents/owner.alias.md",
  "mirror": ["README.md", "chat", "project", "requirements"],
  "skills": ["api-endpoint-auditor", "test-case-generator"]
}

If no mirror exists

If the agent does not have a Mirror Context folder in Stash, the command still creates the local Claude Code agent or Cursor rule from the Camber agent metadata.

No mirror folders are restored until the agent has mirrored context in Camber.