Playground

Playground is a private browser conversation with agents running on your daemons. Open it from an agent page for a single-agent session, or use the Home composer to bring several agents into the same conversation.

What you getCopy Anchor Link

Playground creates a real session on the agent's daemon, using the same runtime, workspace, and tools as a channel conversation. Its output streams into the same kind of session transcript.

You can change supported runtime settings for the next turn without altering the agent's saved configuration, and interrupt a turn when needed.

Configure AgentConnect from a conversationCopy Anchor Link

In a Playground conversation with a single agent, that agent can read your setup and make changes for you with the same tools as the MCP connector. It acts as you, so your role and visibility apply. Each change appears as an approval card above the composer with its exact arguments, and nothing is applied until you choose Approve and run. The agent is then told the result and continues.

Start with the built-in AgentConnect agent for setup work; it comes with skills for the platform and for creating agents. Any agent can also change its own configuration and workspace this way, but it cannot delete itself.

These tools are not available in a conversation with several agents. Adding an agent to a conversation removes them for the rest of that conversation, so start a new single-agent conversation for setup work.

The agent never asks for credentials in chat. To create an agent, connect an integration or code host, or add a secret, MCP server, or skill, it opens the matching console dialog, prefilled where it can, for you to finish. Trying a Decision on a sample message is not available here; use Try with an example in the Decision editor.

Work with several agentsCopy Anchor Link

Add agents before the first message from the Home composer, or add them to an existing Playground conversation.

• A message without an @AgentName goes to every participant. Each agent may answer or stay silent.
• An explicit @AgentName narrows that turn to the named participant or participants.
• Every agent keeps its own configuration while the browser combines their activity into one conversation.

When the session is savedCopy Anchor Link

Opening Playground starts with an empty, temporary view. Your first message saves the private conversation under Sessions, where you can reopen it later.

TipsCopy Anchor Link

• Test permission modes here before using an agent in a shared channel — try Plan or Ask for approval first, watch what it wants to do, then relax.
• The Playground respects the agent's workspace. For a new single-agent conversation backed by GitHub, choose whether its first turn uses an isolated worktree without changing the agent's saved default.
• If the composer reports an agent as unreachable, check its daemon is online — Playground sessions run on the participating daemons, not in the cloud.