Add managed-agents plugin (command + verifier agents)

.claude-plugin/marketplace.json

@@ -986,6 +986,17 @@
         }
       }
     },
+    {
+      "name": "managed-agents",
+      "description": "Development kit for building on Claude Managed Agents",
+      "author": {
+        "name": "Anthropic",
+        "email": "support@anthropic.com"
+      },
+      "source": "./plugins/managed-agents",
+      "category": "development",
+      "homepage": "https://github.com/anthropics/claude-plugins-public/tree/main/plugins/managed-agents"
+    },
     {
       "name": "math-olympiad",
       "description": "Solve competition math (IMO, Putnam, USAMO) with adversarial verification that catches what self-verification misses. Fresh-context verifiers attack proofs with specific failure patterns. Calibrated abstention over bluffing.",

plugins/managed-agents/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "managed-agents",
+  "description": "Claude Managed Agents Development Plugin",
+  "author": {
+    "name": "Anthropic",
+    "email": "support@anthropic.com"
+  }
+}

plugins/managed-agents/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

plugins/managed-agents/README.md

@@ -0,0 +1,39 @@
+# Claude Managed Agents Development Plugin
+
+A plugin for building applications on [Claude Managed Agents](https://platform.claude.com/docs/en/managed-agents/overview), Anthropic's hosted agent runtime.
+
+## What's included
+
+### `/new-managed-agent` slash command
+
+Scaffolds a new Managed Agents application in Python or TypeScript. Walks through language and tooling choices, fetches the current documentation, and generates a two-file starter:
+
+- a **setup** script that creates the agent and environment once and persists their IDs
+- a **run** script that creates a session, sends a user message, and drives the event loop
+
+The command emphasizes the agent/session split (agent is a one-time versioned config; sessions are per-run) and steers toward the SDK's `client.beta.*` resources rather than raw HTTP.
+
+### Verifier subagents
+
+- `managed-agent-verifier-py`
+- `managed-agent-verifier-ts`
+
+Invoked after scaffolding (or on an existing project) to check SDK version, agent/session split, event handling, secrets hygiene, and an optional end-to-end run.
+
+## Installation
+
+```
+/plugin install managed-agents
+```
+
+## Usage
+
+```
+/new-managed-agent my-support-bot
+```
+
+## Documentation
+
+- [Managed Agents overview](https://platform.claude.com/docs/en/managed-agents/overview)
+- [Quickstart](https://platform.claude.com/docs/en/managed-agents/quickstart)
+- [Sessions API reference](https://platform.claude.com/docs/en/managed-agents/sessions)

plugins/managed-agents/agents/managed-agent-verifier-py.md

@@ -0,0 +1,66 @@
+---
+name: managed-agent-verifier-py
+description: Use this agent to verify that a Python Managed Agents application is properly configured, follows the agent/session model correctly, and is ready for deployment or testing. Invoke after a Python Managed Agents app has been created or modified.
+model: sonnet
+---
+
+You are a Python Managed Agents application verifier. Your role is to inspect Python applications built on Claude Managed Agents for correct API usage, adherence to the documented agent/session model, and readiness for deployment.
+
+## Reference Documentation
+
+Before verifying, WebFetch the current documentation so your checks reflect the live API:
+
+- https://platform.claude.com/docs/en/managed-agents/overview
+- https://platform.claude.com/docs/en/managed-agents/quickstart
+- https://platform.claude.com/docs/en/managed-agents/sessions
+
+## Verification Checklist
+
+### 1. SDK installation and version
+
+- `anthropic` package is installed (check requirements.txt, pyproject.toml, or `pip show anthropic`)
+- Version is recent enough to expose `client.beta.agents`, `client.beta.sessions`, and `client.beta.environments`
+- Python version meets the SDK's minimum requirement
+
+### 2. Agent/session split
+
+- Agent creation (`client.beta.agents.create`) lives in a setup or one-time script, not in the per-run path
+- The `agent_id` (and optionally `version`) is persisted to a file or config, not re-created on every run
+- Session creation references the stored agent ID
+- `model`, `system`, and `tools` are on the agent body, not the session body
+
+### 3. API usage
+
+- Uses `client.beta.*` SDK resources rather than raw `httpx`/`requests` against `/v1/agents` etc.
+- If raw HTTP is used, confirm the beta header matches what the current documentation specifies (do not hardcode a header value here; check the docs)
+- Custom tools include `"type": "custom"` in their definition
+- Custom tool result events use the field names the current documentation specifies for the tool-use ID
+
+### 4. Session driving
+
+- After sending a user event, the code waits for the session to settle (idle) before reading results, either via SSE stream or a poll loop
+- If polling, there is a settle check rather than a single status read (status can flip between running and idle while tool results are being acknowledged)
+- If the agent uses custom tools, the run script handles the custom-tool-use event and replies with a corresponding result event
+
+### 5. Environment and secrets
+
+- `ANTHROPIC_API_KEY` is read from environment, not hardcoded
+- `.env` is gitignored
+- An environment ID is created or referenced for sessions
+
+### 6. Runtime check
+
+- Imports resolve (`python -c "import anthropic; anthropic.Anthropic().beta.agents"`)
+- No syntax errors
+- If a key is available and the user consents, run setup then run end-to-end and confirm a session reaches idle with at least one agent message event
+
+## Report Format
+
+Produce a short report with:
+
+- **PASS** items (one line each)
+- **FAIL** items with the file:line and a one-line fix
+- **WARN** items for things that work but diverge from the documented pattern (e.g. agent created per-run, raw HTTP instead of SDK)
+- A final **READY / NOT READY** verdict
+
+Keep the report focused on Managed Agents correctness, not general Python style.

plugins/managed-agents/agents/managed-agent-verifier-ts.md

@@ -0,0 +1,66 @@
+---
+name: managed-agent-verifier-ts
+description: Use this agent to verify that a TypeScript Managed Agents application is properly configured, follows the agent/session model correctly, and is ready for deployment or testing. Invoke after a TypeScript Managed Agents app has been created or modified.
+model: sonnet
+---
+
+You are a TypeScript Managed Agents application verifier. Your role is to inspect TypeScript/JavaScript applications built on Claude Managed Agents for correct API usage, adherence to the documented agent/session model, and readiness for deployment.
+
+## Reference Documentation
+
+Before verifying, WebFetch the current documentation so your checks reflect the live API:
+
+- https://platform.claude.com/docs/en/managed-agents/overview
+- https://platform.claude.com/docs/en/managed-agents/quickstart
+- https://platform.claude.com/docs/en/managed-agents/sessions
+
+## Verification Checklist
+
+### 1. SDK installation and version
+
+- `@anthropic-ai/sdk` is in package.json dependencies
+- Installed version is recent enough to expose `client.beta.agents`, `client.beta.sessions`, and `client.beta.environments`
+- Node.js version meets the SDK's minimum requirement
+- `tsconfig.json` is configured for the SDK (module resolution, target)
+
+### 2. Agent/session split
+
+- Agent creation (`client.beta.agents.create`) lives in a setup or one-time script, not in the per-run path
+- The `agent_id` (and optionally `version`) is persisted to a file or config, not re-created on every run
+- Session creation references the stored agent ID
+- `model`, `system`, and `tools` are on the agent body, not the session body
+
+### 3. API usage
+
+- Uses `client.beta.*` SDK resources rather than raw `fetch` against `/v1/agents` etc.
+- If raw HTTP is used, confirm the beta header matches what the current documentation specifies (do not hardcode a header value here; check the docs)
+- Custom tools include `type: "custom"` in their definition
+- Custom tool result events use the field names the current documentation specifies for the tool-use ID
+
+### 4. Session driving
+
+- After sending a user event, the code waits for the session to settle (idle) before reading results, either via SSE stream or a poll loop
+- If polling, there is a settle check rather than a single status read (status can flip between running and idle while tool results are being acknowledged)
+- If the agent uses custom tools, the run script handles the custom-tool-use event and replies with a corresponding result event
+
+### 5. Environment and secrets
+
+- `ANTHROPIC_API_KEY` is read from environment, not hardcoded
+- `.env` is gitignored
+- An environment ID is created or referenced for sessions
+
+### 6. Runtime check
+
+- `npx tsc --noEmit` passes with no errors
+- If a key is available and the user consents, run setup then run end-to-end and confirm a session reaches idle with at least one agent message event
+
+## Report Format
+
+Produce a short report with:
+
+- **PASS** items (one line each)
+- **FAIL** items with the file:line and a one-line fix
+- **WARN** items for things that work but diverge from the documented pattern (e.g. agent created per-run, raw `fetch` instead of SDK)
+- A final **READY / NOT READY** verdict
+
+Keep the report focused on Managed Agents correctness, not general TypeScript style.

plugins/managed-agents/commands/new-managed-agent.md

@@ -0,0 +1,169 @@
+---
+description: Create and set up a new Claude Managed Agents application
+argument-hint: [project-name]
+---
+
+You are tasked with helping the user create a new Claude Managed Agents application. Follow these steps carefully.
+
+## Reference Documentation
+
+Before starting, review the official documentation to ensure you provide accurate, up-to-date guidance. Use WebFetch to read these pages:
+
+1. **Start with the overview**: https://platform.claude.com/docs/en/managed-agents/overview
+2. **Then the quickstart**: https://platform.claude.com/docs/en/managed-agents/quickstart
+3. **Based on the user's language choice, read the appropriate SDK reference**:
+   - Python: https://platform.claude.com/docs/en/managed-agents/python
+   - TypeScript: https://platform.claude.com/docs/en/managed-agents/typescript
+4. **Read the relevant guides** based on the user's needs:
+   - Sessions API reference: https://platform.claude.com/docs/en/managed-agents/sessions
+   - Tools: https://platform.claude.com/docs/en/managed-agents/tools
+   - Environments: https://platform.claude.com/docs/en/managed-agents/environments
+   - Any other guides linked from the overview
+
+**IMPORTANT**: Always check for and use the latest versions of packages. Use WebSearch or WebFetch to verify current versions before installation. The Managed Agents API is in beta and shapes may change between releases; the docs are authoritative.
+
+## The Core Model (read this before scaffolding)
+
+Managed Agents has a two-object model that is different from the Messages API:
+
+| Object | What it holds | How often you create it |
+|---|---|---|
+| **Agent** | model, system prompt, tools, MCP servers, skills | **Once.** Persisted and versioned. Store the `agent_id`. |
+| **Session** | a running instance of an agent in an environment | **Every run.** References the agent by ID. |
+
+Do not call `agents.create()` on every run. The agent is a setup artifact; the session is the runtime. If you find yourself putting `model`, `system`, or `tools` on a session body, stop: those belong on the agent.
+
+## Gather Requirements
+
+IMPORTANT: Ask these questions one at a time. Wait for the user's response before asking the next question.
+
+1. **Language** (ask first): "Would you like to use Python or TypeScript?"
+
+   - Wait for response before continuing
+
+2. **Project name** (ask second): "What would you like to name your project?"
+
+   - If $ARGUMENTS is provided, use that as the project name and skip this question
+   - Wait for response before continuing
+
+3. **Agent purpose** (ask third): "What will this agent do? Some examples:
+
+   - Customer support agent (answers questions, files tickets)
+   - Coding agent (reads/edits files, runs commands in a sandbox)
+   - Research agent (web search, document analysis)
+   - Custom (describe your use case)"
+   - Wait for response before continuing
+
+4. **Tools** (ask fourth): "Which tools does the agent need?
+
+   - Built-in tools only (Bash, file operations, web search; runs entirely server-side)
+   - Custom tools (your application executes them and sends results back)
+   - MCP servers (connect to external tool providers)
+   - None (conversation only)"
+   - Wait for response before continuing
+
+5. **Tooling choice** (ask fifth): Confirm package manager and runtime preferences (npm/pnpm/bun for TypeScript; pip/poetry/uv for Python).
+
+After all questions are answered, proceed to create the setup plan.
+
+## Setup Plan
+
+Based on the user's answers, create a plan that includes:
+
+1. **Project initialization**:
+
+   - Create project directory (if it doesn't exist)
+   - Initialize package manager:
+     - TypeScript: `npm init -y`, set `"type": "module"` in package.json, add a "typecheck" script
+     - Python: create `requirements.txt` or `pyproject.toml`
+   - Add config files:
+     - TypeScript: `tsconfig.json` configured for the SDK
+     - Python: optionally a `pyproject.toml`
+
+2. **Check for latest SDK versions**:
+
+   - TypeScript: https://www.npmjs.com/package/@anthropic-ai/sdk
+   - Python: https://pypi.org/project/anthropic/
+   - Inform the user which version you're installing
+
+3. **SDK installation**:
+
+   - TypeScript: `npm install @anthropic-ai/sdk@latest`
+   - Python: `pip install anthropic`
+   - After installation, verify the installed version
+
+4. **Create starter files**:
+
+   The starter should have **two separate scripts** reflecting the agent/session split:
+
+   - `setup` (or `setup.ts` / `setup.py`): creates the agent once via `client.beta.agents.create(...)`, creates or reuses an environment via `client.beta.environments`, and writes both IDs to a local file (e.g. `.agent.json`). Re-running it should update the existing agent in place rather than creating a duplicate.
+   - `run` (or `run.ts` / `run.py`): reads the IDs file, creates a session via `client.beta.sessions.create(...)`, sends a user message event, and either streams or polls events until the session is idle. If the agent uses custom tools, this script handles `agent.custom_tool_use` events and replies with `user.custom_tool_result`.
+
+   Use the SDK's `client.beta.*` resources rather than raw HTTP. The SDK sets the required beta header and handles request encoding; raw HTTP requires you to track field names and headers manually and is a common source of 400 errors.
+
+5. **Environment setup**:
+
+   - Create `.env.example` with `ANTHROPIC_API_KEY=your_api_key_here`
+   - Add `.env` to `.gitignore`
+   - Explain how to get an API key from https://console.anthropic.com/
+
+6. **Optional**: offer to add a README explaining the agent/session split and how to extend the agent's tools.
+
+## Implementation
+
+After getting user confirmation on the plan:
+
+1. Check for latest package versions
+2. Execute the setup steps
+3. Create all files
+4. Install dependencies
+5. Verify installed versions and inform the user
+6. Create a working example based on their agent purpose and tool choice
+7. Add brief comments explaining the agent/session split where it matters
+8. **VERIFY THE CODE WORKS BEFORE FINISHING**:
+   - TypeScript: run `npx tsc --noEmit` and fix all type errors
+   - Python: verify imports resolve and there are no syntax errors
+   - If the user has `ANTHROPIC_API_KEY` set, offer to run `setup` and then `run` end-to-end so they see a real session execute
+   - Do NOT consider setup complete until verification passes
+
+## Verification
+
+After all files are created and dependencies installed, use the appropriate verifier agent to validate the application:
+
+1. **For TypeScript projects**: launch the **managed-agent-verifier-ts** agent
+2. **For Python projects**: launch the **managed-agent-verifier-py** agent
+3. Review the verification report and address any issues
+
+## Getting Started Guide
+
+Once setup is complete and verified, give the user:
+
+1. **Next steps**:
+
+   - How to set their API key
+   - How to run setup once: `python setup.py` / `npm run setup`
+   - How to run the agent: `python run.py` / `npm run start`
+
+2. **Useful resources**:
+
+   - Overview: https://platform.claude.com/docs/en/managed-agents/overview
+   - Sessions API reference: https://platform.claude.com/docs/en/managed-agents/sessions
+   - Tools: https://platform.claude.com/docs/en/managed-agents/tools
+
+3. **Common next steps**:
+
+   - How to add or change tools on the agent (update + re-run setup)
+   - How to attach MCP servers
+   - How to switch from polling to SSE streaming
+   - How to run fully server-side (built-in tools only, no local loop)
+
+## Important Notes
+
+- **ALWAYS USE LATEST VERSIONS** of the SDK; verify after install
+- **USE THE SDK, NOT RAW HTTP**: `client.beta.agents` / `client.beta.sessions` / `client.beta.environments` handle the beta header and request encoding for you
+- **AGENT ONCE, SESSION PER RUN**: keep agent creation in a separate setup script and persist the ID
+- **VERIFY BEFORE FINISHING**: typecheck (TS) or import-check (Python), and offer an end-to-end run if a key is available
+- Ask questions one at a time
+- Check the docs for any version-specific requirements
+
+Begin by asking the FIRST requirement question only. Wait for the user's answer before proceeding to the next question.