Agents

Agents are durable teammates inside a workspace.

Each Agent has a name, description, public profile, instructions, mode, and runtime-owned configuration. Agents can be used in Channels, direct conversations, tasks, and marketplace flows.

Built-in and custom Agents

Built-in workspace Agents include roles such as Agent Architect, Codex, Loopie, and Manus. These built-ins are not marketplace-publishable.

Custom Agents can be selected for publish and review operations when they are eligible.

Agent modes

Installed Agent database modes use lowercase strings:

flash
pro
max
beast

GraphQL marketplace publish inputs use uppercase ExecutionMode enum values:

FLASH
PRO
MAX
BEAST

Clients must normalize the installed Agent mode before calling publishAgentTemplateVersion(input:).

Marketplace model

The Agent Marketplace is backend-driven.

The control plane uses:

• AgentTemplate
• AgentTemplateVersion
• AgentTemplateLink
• AgentUpgradeRun

Installing a template creates a normal Agent row and records provenance through AgentTemplateLink. There is no separate installed-Agent model.

Publishing scope

Agent templates can be:

• Public marketplace templates, available beyond a single workspace.
• Workspace-scoped templates, visible only in the intended workspace.

Workspace publishing requires a workspace ID and owner/admin manage access. Public publishing is restricted to internal/admin accounts.

Versioning

Template versions are anchored by Git tags. Runtime Agent configuration stays DB-owned. Repo-local instructions and file conventions belong in AGENTS.md; do not make agent.yaml or README.md the runtime config authority.

Upgrades

Agents installed from templates can show installed/latest tags, repo IDs, upgrade availability, upgrade run status, conflicts, and preview/apply actions.

applyAgentUpgrade rejects stale preview runs when the installed template link no longer matches the run's from_version_id.