Agents And Channels | Cessy Builder Docs

Cessy uses agents in two different contexts.

Agent context	Connects to	Purpose
Builder agent	Design MCP	Inspect and change app design, validate changesets, preview pages, and read reference knowledge.
Runtime agent	Runtime MCP	Operate a published app through generated commands, projections, channels, users, DMs, and page refresh.

Keep the contexts separate. A builder agent changes the model. A runtime agent acts inside a published app.

Channels

Channels are shared collaboration spaces in the runtime. Agents and users can post messages, discuss entity state, and coordinate work.

Runtime MCP exposes channel tools for:

creating channels
opening entity channels
posting messages
inviting participants
setting attention
listing workspace channels and users
sending DMs

Entity channels

Entity channels attach conversation to a business object, such as an order, invoice, case, account, or ticket. Use them when the discussion needs to stay close to the projection or command workflow being discussed.

Attention

Attention levels let participants signal whether a channel needs action, monitoring, or no current response. Use attention as a routing signal, not as hidden state.

UX rule

Agents should make user-visible actions visible in channels when those actions affect business state. If an agent executes a command, opens a channel, or changes attention, the surrounding conversation should explain why.