Skip to Content
🚀 Design Partner Program — Limited spots available →

AI Agents

The AI Agents screen is your fleet view. Each assistant is a card. The grid shows everything that is running and how it is behaving.

Permission required: Manage organisation.

The four assistant types

TypeWhat it doesExample
SupervisorTop-level coordinator. Routes work to specialists, owns the response frame.Service Economics Supervisor.
SpecialistDeep-domain expert. Owns one signal type and builds memory of patterns over time.Margin Watch, SLA Sentinel, Capacity Coach.
PatternStateless detector. Runs against fresh data and emits signals.Cost Anomaly Detector.
AmbientAlways-on listener. Surfaces events to the supervisor when they matter.Recording Stream Listener.

Anatomy of a card

ElementMeaning
VisualSlug-based icon (Coins for finance, ShieldAlert for risk, Users for capacity, Bell for alerts, BookOpen for learning).
Name and slugHuman-friendly name and the technical slug used in policies.
Type badgeSupervisor, Specialist, Pattern, or Ambient.
Autonomy tierObserve, Assist, Act, or Custom.
HealthHealthy, Needs attention, or Paused.
TriggerSchedule (cron-like) or event (for example, on recording).
CooldownMinimum seconds between runs to avoid thrashing.
Specialist chainFor supervisors: which specialists they call.

Autonomy tiers

Each assistant ships with a recommended tier; you can override per assistant. Tiers map to default policy bundles applied by Policies.

TierWhat it can doWhen to use
ObserveDetect signals only. Log to Pulse. Never propose responses.Onboarding, low-trust phase.
AssistDetect, propose responses, draft summaries. Always asks before applying.Default for most organisations.
ActDetect and auto-apply responses within configured guardrails.High-trust, mature operations.
CustomPer-workflow rules set in Policies.Power users.

Tiers are a starting point. Real autonomy is decided per workflow in Policies.

Hire, pause, retire

  • Hire. Enable an assistant from the catalogue. New assistants start in Observe.
  • Pause. Temporarily stop an assistant. Cards turn grey and signals it would have produced are not generated.
  • Retire. Remove the assistant. History is kept.

Sub-pages

PageCovers
Agent ProfilesDetail page for one assistant: operator and developer views.
Specialist MemoryLearned patterns, review queue, version history.
Delivery ChannelsSend output to Teams, Slack, or email.