AgentPlayground
Docs
Playgrounds

A playground is an organizational container — a way to group teams together by context so your
agent setup doesn't turn into one long undifferentiated list. A "Personal" playground might hold a
trainer, a nutritionist, and a finance advisor; a "Business" playground might hold sales, content,
and operations teams. You can have as many playgrounds as you want.

What a playground holds
  • A name, icon, and color — how it shows up in the Playgrounds list.
  • A set of team IDs — the teams grouped into it. Teams aren't copied or duplicated; a playground just references the teams that belong to it, so a team can in principle be part of more than one playground.
  • Brain tags — the set of Brain tags this playground's Brain view is scoped to. This is what keeps a Personal playground's notes separate from a Business playground's notes, even though they're stored in the same underlying vault.
  • A layout — the order of dashboard widgets and workspace menu items, customizable per playground.
Opening one

The Playgrounds view (in the sidebar) shows the different playgrounds and nothing else — click one
to enter it. Inside, you get that playground's own dashboard: its teams, their active tasks, their
skills, and recent completions, plus a Brain view scoped to just that playground's tagged notes.

Creating a playground

The fastest way is to ask through the same chat-assisted panel available from both the sidebar's
"New playground" button and the Playgrounds page itself — describe what it's for, and it proposes a
configuration (matching existing teams where it can, and suggesting Brain tags) that you confirm
before it's created. You can also build one from a Library pack — see
Browse & install packs — which creates a playground pre-loaded with a
team, its agents, and its skills in one step.

Quick task routing

The Playgrounds view also has a Quick task button: describe a task in plain language, the
coordinator picks the best-fit team across your whole install (with reasoning shown), and once you
confirm — or override its pick — the task runs in the background.

Playgrounds vs. Projects

Playgrounds are meant to be long-lived — your ongoing personal or business setup. If you need an
isolated, disposable workspace instead — its own file folder, its own Brain namespace, teams
borrowed by reference, and a one-tap teardown that leaves nothing behind — that's a Project, a
separate concept covered elsewhere in the app. Reach for a playground when you're organizing
standing teams; reach for a project when you want a scoped, throwaway workspace for one goal.