What problem does it solve?
Launching a Claude Managed Agent requires assembling four ordered API payloads (environment, agent, session, kickoff) and executing them in sequence with correct ID chaining, all while keeping the Anthropic API key out of files, logs, and chat. Doing this by hand is error-prone and risks leaking credentials.
Core Features & Use Cases
- Payload Generation: Convert a validated build-sheet.json into the four ordered CMA API payloads, with permission policies baked in (agent toolsets always_allow, MCP servers always_ask).
- Resumable Launch Script: Write a launch.sh that creates environment → agent → session → kickoff in order, chaining IDs and resuming from the last created resource on re-run, reading $ANTHROPIC_API_KEY only at runtime.
- Pre-Launch Validation: Run a validator that checks required fields, placeholder integrity, outcome rubrics, and scans all payloads and launch.sh for embedded API keys, failing the launch on any leak.
- Use Case: After planning an agent with the interview phase, run the three scripts to produce payloads and launch.sh, validate them, then export your key and execute launch.sh to bring the agent online.
Quick Start
Ask the AI to generate the launch payloads and launch script from my build-sheet.json, validate them for key leaks, and walk me through launching with my own Anthropic API key.