# Set up Arena with a coding agent

> Give Codex, Claude Code, Cursor, or another agent the exact setup task.

Audience: Developers using coding agents
Updated: 2026-08-02
Page: /docs/ai-handoff

## Copy the setup prompt

Choose Copy for AI at the top of this guide—or any HIM guide—then paste the prompt into your coding agent from the repository you want to connect. The generated prompt includes absolute links back to the current Arena docs.

- [llms.txt](/llms.txt) — Compact product, contract, and guide index.
- [Full docs as Markdown](/docs/llms-full.txt) — All in-product docs from the same typed source.
- [Public schemas](/docs/him-package) — Start with the package and contract boundary.

The agent should inspect the repository, identify its real headless command and result video, run a small test, and show the safe upload inventory. It must stop for your approval before uploading. A .him overlay is optional and should only be created when you explicitly request the advanced package workflow.

## Repository integration prompt

**Use with Claude Code, Codex, Cursor, or another coding agent**

```text
Read the Quickstart and CLI guides linked in the copied prompt.

Goal: test this existing robotics project and upload its policy, simulator, or both with the real MP4 it produced.

Rules:
- Inspect the repository first. Do not read .env files, credentials, tokens, or large model/data files.
- Preserve the native simulator, trainer, commands, and source layout.
- Run the shortest meaningful test and inspect result.mp4. Do not invent metrics or hardware claims.
- Build a safe ZIP that excludes secrets, data, weights, checkpoints, logs, caches, environments, and .git.
- Show the run command, test evidence, ZIP inventory, sizes, name, and caption; ask before uploading.
- After approval, use him upload with --video, --kind, --robot, --name, --caption, --run-command, --yes, and --json.
- Do not create .him or launch paid compute unless I explicitly request the advanced workflow.
- Return the project URL, upload ID, exact artifacts, and limitations.
```

## Simulator intake prompt

**Use before a MuJoCo or Isaac integration**

```text
Read the MuJoCo or Isaac guide linked in the copied prompt. Inspect this simulator project without reading secrets. Identify the smallest native headless command, robot assets, task launcher, output video, licenses, and runtime requirements. Run the smallest local smoke test, inspect the real MP4, prepare a safe source ZIP, and show the complete inventory before requesting approval for him upload. Use .him only if I explicitly request immutable packaging or controlled scoring.
```

## A good agent handoff returns

- Files inspected and the exact source archive and video used.
- Facts learned versus assumptions/unknowns that still require a human.
- The verified run command, test evidence, ZIP inventory, video details, and public caption.
- Commands proposed, which were actually executed, and their exact results.
- Security, license, privacy, simulator, timing, and hardware limitations.
- The next smallest safe action—not a broad rewrite or hidden provider deployment.