Glossary
The platform concepts used to connect context, organize work, and extend Studio.
Studio is the horizontal platform. These terms describe its workspaces, connections, agents, and extension model. Website configuration and commerce terminology belong to Storefront.
Work and context
Organization
The shared workspace for members, roles, connections, credentials, and settings. See Key concepts.
Project
The context for a repository, application, or other piece of work. Its connected systems and available views determine what people and agents can use.
Agent
A configured role with instructions and selected connection tools. People can interact with it in Studio; its virtual MCP endpoint also makes selected capabilities available to external clients. See Agents.
Connection
An organization-level integration with an MCP server. It makes that server's tools and resources available according to the connection's authentication and access rules. See Connections.
Thread
A saved conversation with its messages, tool results, and execution context. See Context and tasks.
Task
A requested outcome with context, acceptance criteria, progress, and feedback. Repository tasks can produce changes for review; other tasks can produce research, data, or actions through connected tools. See Tasks.
Automation
An agent run started by a schedule or configured event. See Automations.
Tools and interfaces
Tool
An operation an agent or MCP client can call with defined inputs. Its result can be structured data, text, or another supported MCP result. See Building tools.
Resource
Data identified by a URI and exposed by an MCP server. An MCP App resource can serve the HTML interface associated with a tool. See Resources.
App
An MCP App is an interactive interface linked to a tool through an MCP resource. Studio hosts it alongside the conversation or as an available project view. This is the generic extension model; the Site Editor is one Storefront application of it. See Building MCP Apps.
Virtual tool
A reusable JavaScript operation attached to an agent. It can transform data or combine downstream connection tools in a sandbox. See Creating tools.
Virtual MCP
The MCP endpoint representing an agent's selected tools, resources, and instructions. It lets external clients use those capabilities through Studio. See API keys.
Execution and delivery
Sandbox
An execution environment for code and repository work. Hosted Studio uses AgentSandbox; the desktop app runs native harnesses and worktrees through its local API. See Architecture.
Daemon
The sandbox process that provides filesystem, Git, shell, setup, and preview operations. It is part of the execution environment, separate from the Studio API.
Harness
The program driving an agent's execution loop. Hosted and desktop runtimes support different harnesses. See Where an agent runs.
Review
The assessment of a task's result against its requested outcome. Repository work can use a pull request, checks, and a preview; delivery lanes depend on the organization's configuration. See Reviews and QA.
Upstream capabilities
Signal
An observation from a connected system that could justify work. Diagnosis is currently on demand; continuous monitoring is in build. See Signals.
Objective
A proposed goal with a metric and budget for evaluating work. Objectives are planned, rather than an available end-to-end prioritization loop. See Objectives.
Website terminology
Definitions for sections, loaders, blocks, commerce adapters, and website runtime packages live in the Blocks 7.x glossary. The previous deco.cx admin is retired; its historical documentation is retained for migration reference.