Agent-native Campaign input

Agent Handoff

Send product evidence, promotional reference material, local screenshots, demos, and advisory Campaign tasks from Codex, Claude Code, OpenClaw, or CI. Every Handoff is reviewed in OtterZero before it can influence Campaigns.

1. Create one client token

Open Settings → Agent Integrations. Create a selected-Agent token by default, or explicitly choose all current and future Agents. The secret is displayed once. One token and one MCP configuration can route to every authorized Agent using agent_id.

2. CLI Quick Start (Stable)

The CLI is the recommended integration. It works directly from terminals, coding Agents, and CI without MCP.

npm install -g @otterzero/agent-handoff
export OTTERZERO_API_TOKEN="oz_pat_example_only"
otterzero doctor --json
otterzero agents list --json
otterzero context --agent-id agent_example_123 --json
otterzero validate ./handoff.json --json
otterzero submit ./handoff.json --json --no-interactive
otterzero status handoff_example_123 --json

3. Install the portable Skill (Stable)

The Skill teaches an external Agent when to inspect context, construct a manifest, submit through the CLI, and explain the human-review boundary. It contains no token or transport implementation.

otterzero skill-install --provider codex --scope user

Providers: codex, claude, and openclaw. Use --scope project for repository-local installation and --force only when replacing an existing Skill.

4. MCP configuration (Beta, optional)

MCP exposes the same shared client and submission orchestrator. It is configured once per client/device and never replaces the CLI.

{
  "mcpServers": {
    "otterzero": {
      "command": "otterzero-mcp",
      "env": {
        "OTTERZERO_API_TOKEN": "oz_pat_example_only",
        "OTTERZERO_API_URL": "https://api.otterzero.com/api/v1"
      }
    }
  }
}

Tools: list_otterzero_agents, get_otterzero_context, get_otterzero_snapshot, list_otterzero_attention, get_otterzero_campaign, submit_handoff, and get_handoff_status.

Two Handoff workflows

  • Campaign reference: product facts, release notes, positioning, product-introduction copy, screenshots, demos, or PDFs. Everyday promotional copy is generation reference, not a publish command.
  • Campaign plan proposal: advisory tasks for the next planning cycle. OtterZero Brain validates, modifies, rejects, or adopts each task and persists the only canonical Campaign Plan.

Security, limits, and troubleshooting

  • Never place tokens or credentials in manifests, repositories, or Agent messages.
  • Attachments must be local JPEG, PNG, WebP, GIF, or PDF files up to 10 MB. Remote URL ingestion and video are not supported.
  • External clients cannot approve, schedule, publish, or replace an active Plan.
  • 401: token missing, expired, or revoked. 403: Agent or Campaigns entitlement not authorized. 409: invalid lifecycle state or idempotency conflict.
  • Run otterzero doctor --json, then rediscover Agent IDs after token-scope changes.