**Status: the workflow below is real and works today; a dedicated "download source" button
alongside the Docker image is still a backlog item** — for now, the source you customize is the
same repository the packaged app is built from.

The packaged desktop app (Docker image + start.bat/start.sh) is meant to just run. But
everything it does — which teams exist, what the coordinator's prompt says, what the sidebar looks
like, what an agent's instructions are — is source code you can read and change. If you're
comfortable pointing an AI coding assistant at a folder, you can customize your own copy of
AgentPlayground the same way you'd customize any other codebase.

1. Get the source. Today that means the same project checkout the app is built from (clone or copy the repository) rather than a separate stripped-down "source download" — that packaging convenience is on the roadmap but not built yet.
2. Open it in Claude Code (claude in the project folder, or the desktop/IDE app pointed at the folder).
3. Read [Architecture overview](/docs/architecture-overview) and [Key files map](/docs/key-files-map) first — or just tell Claude Code to read them; they're real files in docs/ and lib/docs/pages/, not just web copy, so an assistant working in your checkout can read them directly.
4. Describe what you want changed in plain language — "add a team called X that does Y", "make the sidebar always show Z", "change the brand color to purple." Claude Code can read the relevant registry/catalog file (see Key files map), make the edit, and verify the build.
5. Rebuild and restart your local install to see the change — npm run build (or the project's Docker rebuild command) the same way any other code change here would be applied.

Safe, low-risk changes an assistant can make confidently by following this doc set: adding a team/
agent/skill, changing design tokens, adding a page to this docs site, adjusting sidebar/widget
layout defaults, adding a Prompt Template.

Higher-risk changes worth double-checking before applying: anything touching
prisma/schema.prisma (schema changes need to stay additive — no dropped/renamed columns without
a real migration plan), auth/middleware.ts (breaking the public-route allowlist can lock you out
or expose something), and the Docker build config (output: 'standalone' must keep working).

If what you want is a genuinely new page/feature (not a new team or a tweaked prompt), that's a
different, slightly bigger task — see downloads/playground-app-template/ (a starter kit + a
ready-made prompt for Claude Code) and Build your own pack for the
smaller, no-code version (a new playground made of teams/agents/skills).

• Architecture overview
• Key files map
• Add a team, agent, or skill