# Studio

> Storefront documents the Blocks framework, the Site Editor app, website templates, and commerce integrations.
> Studio documents the extensible platform: context, tasks, sandboxes, connectors, and MCP Apps.
> Blocks 7.x is the released default. Blocks Next is an unreleased proposal; Fresh and the former admin are retired.
> Site Editor publishing follows Git changes, a pull request, review or merge, and the configured deployment. Runtime content reload APIs are separate delivery capabilities.
> Respect availability labels. Do not describe preview, planned, or in-build APIs as available.

Any documentation page is available as Markdown by appending `.md` to its URL.

## Scoped indexes

- [Storefront — current](https://docs.decocms.com/storefront/llms.txt)
- [Studio](https://docs.decocms.com/studio/llms.txt)
- [Site Editor](https://docs.decocms.com/storefront/editor/llms.txt)
- [Templates and storefront implementation](https://docs.decocms.com/storefront/templates/llms.txt)
- [Blocks 7.x — current](https://docs.decocms.com/storefront/blocks/v7/llms.txt)
- [Blocks Next — UNRELEASED PREVIEW](https://docs.decocms.com/storefront/blocks/next/llms.txt)
- [Fresh — retired runtime archive](https://docs.decocms.com/storefront/blocks/fresh/llms.txt)
- [Former admin — retired archive](https://docs.decocms.com/storefront/legacy/llms.txt)

## Studio — Getting started

- [What is Studio](https://docs.decocms.com/studio/get-started/what-is-deco.md): An extensible platform for connecting context, organizing work, and running agents
- [Quickstart](https://docs.decocms.com/studio/get-started/quickstart.md): From zero to a working agent in 5 minutes
- [Key concepts](https://docs.decocms.com/studio/get-started/core-concepts.md): How deco Studio is organized and how the pieces fit together
- [Architecture](https://docs.decocms.com/studio/get-started/architecture.md): How Studio is wired end to end — edge, cloud cluster, and desktop — and how requests, runs, and sandboxes flow between the tiers.

## Studio — Workflows and delivery

- [Workflows and delivery](https://docs.decocms.com/studio/agency/overview.md): Connect signals and context to tasks, execution, and review
- [Tasks & the board](https://docs.decocms.com/studio/agency/tasks.md): Where demand becomes work — the columns, the repository, the pull request, the preview
- [Writing a task](https://docs.decocms.com/studio/agency/writing-a-task.md): Removing ambiguity before an agent starts — the highest-leverage thing you do here
- [Reviews & QA](https://docs.decocms.com/studio/agency/reviews-and-qa.md): How a change gets checked before and after it ships
- [Signals & monitoring](https://docs.decocms.com/studio/agency/signals.md) [IN BUILD]: How problems get found before you report them
- [Objectives](https://docs.decocms.com/studio/agency/objectives.md) [NOT BUILT YET]: A goal with a metric and a budget, per project — what tasks get measured against

## Studio — Connections and agents

- [Agents](https://docs.decocms.com/studio/agents/overview.md): The working surface of Studio — one agent, one job, its own thread history and tools
- [Connections](https://docs.decocms.com/studio/agents/connections.md): Connect tools and services to Studio — once, securely, for your whole team
- [Automations](https://docs.decocms.com/studio/agents/automations.md): Run an agent on a schedule or in response to an event — without a human in the loop
- [AI Providers](https://docs.decocms.com/studio/agents/ai-providers.md): Connect the AI models that power Decopilot and your agents
- [Monitoring](https://docs.decocms.com/studio/agents/monitoring.md): See every tool call your agents make — who, what, when, and how it performed
- [Overview](https://docs.decocms.com/studio/agents/decopilot/overview.md): The AI assistant built into deco Studio
- [Context and tasks](https://docs.decocms.com/studio/agents/decopilot/context-and-tasks.md): How Decopilot manages memory and how to use subtasks for heavy work
- [Tools](https://docs.decocms.com/studio/agents/decopilot/tools.md): What Decopilot can do, and the two kinds of tools it has access to
- [Voice mode](https://docs.decocms.com/studio/agents/decopilot/voice-mode.md): Talk to the current Studio agent while keeping the same chat and preview

## Studio — MCP Apps and extensions

- [Creating Agents](https://docs.decocms.com/studio/build/no-code/creating-agents.md): Configure a focused role, instructions, and selected connection tools in Studio
- [Creating Tools](https://docs.decocms.com/studio/build/no-code/creating-tools.md): Add focused virtual tools that combine connected capabilities without scaffolding an MCP server
- [Project Structure](https://docs.decocms.com/studio/build/full-code/project-structure.md): Understand the full-stack TypeScript architecture of MCP Apps on deco
- [Building Tools](https://docs.decocms.com/studio/build/full-code/building-tools.md): Build MCP tools in TypeScript with full type safety
- [Building MCP Apps](https://docs.decocms.com/studio/build/full-code/building-views.md): Build interactive UIs for MCP tools using the MCP Apps SDK
- [Resources](https://docs.decocms.com/studio/build/full-code/resources.md): Serve MCP App UIs and data as MCP resources
- [Deployment](https://docs.decocms.com/studio/build/full-code/deployment.md): Build and deploy your MCP App

## Studio — Data & content

- [Buckets](https://docs.decocms.com/studio/data/buckets.md): Connect your own S3-compatible bucket for CMS assets — and the IAM permissions it needs
- [Library](https://docs.decocms.com/studio/data/library.md): A Drive-like browser for your organization's shared filesystem
- [MCP catalog](https://docs.decocms.com/studio/data/store.md): Find MCPs in the Deco registry

## Studio — Deploy and self-host Studio

- [Quickstart](https://docs.decocms.com/studio/self-hosting/quickstart.md): Run Studio locally or deploy to your infrastructure
- [Authentication](https://docs.decocms.com/studio/self-hosting/authentication.md): Supported auth methods and how to configure them for self-hosting
- [Monitoring](https://docs.decocms.com/studio/self-hosting/monitoring.md): How to persist and query monitoring data in self-hosted deployments
- [Linux Desktop Support](https://docs.decocms.com/studio/self-hosting/linux-desktop-support.md): Supported architecture, prerequisites, and known limitations for the Linux desktop app
- [Docker Compose](https://docs.decocms.com/studio/self-hosting/deploy/docker-compose.md): Deploy deco Studio locally using Docker Compose for testing and development
- [Kubernetes](https://docs.decocms.com/studio/self-hosting/deploy/kubernetes.md): Deploy deco Studio and agent sandboxes on Kubernetes using Helm

## Studio — Reference

- [Glossary](https://docs.decocms.com/studio/reference/glossary.md): The platform concepts used to connect context, organize work, and extend Studio.
- [API Keys](https://docs.decocms.com/studio/reference/api-keys.md): Create scoped API keys to access management tools, proxies, and agents
- [Secrets](https://docs.decocms.com/studio/reference/secrets.md): Store API keys, tokens, and sensitive values — encrypted, scoped, and never returned over the API
- [User Management](https://docs.decocms.com/studio/reference/user-management.md): Control who can access your organization and what they're allowed to do
- [Connection Proxy Endpoint](https://docs.decocms.com/studio/reference/api/connection-proxy.md): Connect MCP clients directly to upstream MCP servers through deco Studio
- [Call an Agent from Your App](https://docs.decocms.com/studio/reference/api/external-agent-integration.md): Drive a Studio agent from an external system with a scoped API key — create a thread, run the agent, stream the response, and read the thread back