# Playground

`agent-sdk serve` hosts a web playground at
`http://127.0.0.1:3000/playground`. When one server hosts multiple
agents, each agent's playground is at `/<slug>/playground` and `/`
lists them.

## Playground surfaces

| Surface | What you can do |
| --- | --- |
| Chat | Text and reasoning stream live, and tool calls appear inline with arguments, output, and errors |
| Slash commands | Run a custom channel route without path parameters from the composer. A `drive` route becomes `/drive <pr-url>`. GitHub and Slack ingress routes are excluded |
| Try | Call a custom channel route from the Agent tab and copy the request as curl |
| Runs | Search the sessions you own and eval runs, then open them in Chat, Trace, Raw, or Evals |
| Evals | List and run filesystem evals |
| Agent | Inspect discovered tools, skills, subagents, MCP connections, channels, and hooks |
| Raw | Inspect the selected session's event stream |
| Logs | Recent server log lines from `GET /v1/logs` |

In `--dev` on loopback, or with `--allow-anonymous`, the session list
includes every principal.

## Remote access

To open the playground through a tunnel or LAN address, start the
server with `--bearer-token <secret>` and paste the token into the
navbar's token field. See [Auth policies](/docs/reference/channels.md#auth-policies).
