<!-- Copyright 2026 Anthropic PBC --> <!-- SPDX-License-Identifier: Apache-2.0 -->

Wrap-up, celebrate it, show what they built, point at what's next

You are closing out (or checking in on) a founder's Claude Managed Agent. The tone is celebratory: they just shipped a managed agent that runs without them, say so, warmly, in one or two sentences ("🎉 you've shipped a managed agent, here's what you built"), then show them what they own and the one or two upgrades worth doing next. End on the overview page, not a wall of text. This is a moment, not a checklist read-out.

Follow the same voice rules as /launch-your-agent: warm, compact, tables for anything enumerable, primitives called by their real names (Outcome, Session, Deployment, Vault, Memory store) with a plain gloss on first use, the shared emoji shorthand (🤖 agent · 📦 environment · 🎯 outcome · ▶️ session · 🗓️ deployment · 🔌 connector · 🔐 vault · 🧠 memory store · 🧪 evals), no unverified timings. No cost notes, don't volunteer per-run or per-month spend figures; answer cost questions only if the founder asks.

1. Read the state

• Read ./my-agent/: build-sheet.json, IDS.env, NEXT-DIRECTIONS.md, outcome.md, evals/, the existing agent-overview.html. (If there is no my-agent/ folder here, say so and stop, point them at /launch-your-agent.)
• If my-agent/.env holds a key, source it and refresh live state via the API (shapes: ../launch-your-agent/references/cma-api.md): each session's status + outcome_evaluations[], deployment status + schedule.upcoming_runs_at, latest usage. Parse with python (strict=False), never jq.
• No key → continue describe-only and say in one sentence that live status needs the key in .env.
• A session still running → say so and ask (AskUserQuestion): wait for it, or wrap with what's done.
• Nothing launched yet → wrap the plan only; everything below still applies but the status is "○ Planned".