Platform
Agents
The three agent roles in Autodeck and how they behave inside a Deck.
Autodeck uses different agent roles instead of pretending every AI interaction is the same. Those roles are usually encountered inside a Deck.
Assistant
An assistant is a conversational helper attached to a Deck or workspace surface.
Typical use:
- explain a result
- answer a question about the current page
- guide a user through the next step
The assistant acts as an advisor, not as an invisible system with unlimited power.
Specialist
A specialist is still conversational, but it is closer to the core product experience.
Typical use:
- Deck-specific workflows where the AI is the main interface
- guided creation or review flows
- focused domain interactions with a narrower toolset
Worker
A worker handles background execution.
Typical use:
- jobs that do not need a live conversation
- scans, exports, processing tasks, or longer-running actions
- execution that should be auditable and resumable
Why this split exists
The role split helps the product stay understandable:
- users know what kind of behaviour to expect
- Decks can adopt the right interaction pattern
- governance stays clearer because the execution model is explicit
Autodeck treats agents as named system actors with permissions, scope, and audit trails. They are not anonymous scripts hidden behind a chat box.