Skip to main content
The managed dashboard rendering typed agent widgets beyond chat: an approval card awaiting a decision, a live status card, a repository change request with a diff, an in-flight progress card, and a navigation hint
The dashboard is the primary managed experience for hosted agents. It gives users a chat surface, approval inbox, event history, and resource-aware widgets without requiring local agent setup.
The managed dashboard experience is rolling out in phases. API resources and generated reference docs are available while some dashboard controls may appear only for enabled workspaces.

​
Configure ambient agents

Ambient agents start from workspace signals instead of a chat message. Configure them when you want Akua to investigate operational signals proactively.
1

Choose an agent

Start from a platform template such as failed-install triage, or create a workspace agent with the skills and grants it needs.
2

Enable ambient mode

Turn on ambient operation for the agent and choose the signals it can receive.
3

Set trigger policy

Pick trigger types such as install failure, degraded cluster, security finding, quota pressure, or cost anomaly. Set a minimum severity and cooldown so repeated signals do not create noisy duplicate work.
4

Set runtime policy

Prefer read-only triage by default. Allow retained runtimes only when the agent may need repository edits, tests, or package-manager work.
5

Review grants and approvals

Give read grants for resources the agent needs to inspect. Keep mutation grants specific, and require approval for sensitive actions such as accepting repository change requests or accessing secrets.
An ambient run should always leave a reviewable summary in its session. The summary explains the trigger, inspected resources, conclusion, next action, and links to related resources.

​
Interpret widgets

Agents can emit typed widgets into the dashboard event stream. Widgets are not separate state stores; they are views over canonical resources such as approval requests, repository change requests, installs, renders, operations, snippets, and documentation links. Widgets may combine multiple resources. For example, a failed-install widget can show the install, recent render, existing repository change request, and prepared next actions in one place.

​
Reactive state

Widgets should stay current from canonical resource state. If a repository change request moves from READY to ACCEPTING, the widget updates from that resource state instead of relying on stale assistant text. When a widget includes an action, the action calls the underlying resource API. Examples:
  • Resolve an approval request.
  • Start a new agent turn with a prepared reply.
  • Create or accept a repository change request.
  • Run an attributed snippet action.
  • Navigate to an install, render, operation, cluster, or repository.
This keeps dashboard behavior, API behavior, and agent behavior aligned.

Ambient agents

Understand ambient trigger concepts and policy boundaries.

Agent API tasks

Use the same resources from the API.