KOSMOY MISSION CONTROL
Govern agents as operational systems, not just prompts.
An agent is more than a prompt. It has identity, permissions, tools, memory, model access, runtime environment, an oversight path, and an evidence trail. Mission Control gives platform teams and operators a fleet view of all of them.
Agent fleet · 6 agents · last 24h
live
| Agent | Owner | Status | Use case | Cost (24h) | Last run | Risk |
|---|---|---|---|---|---|---|
| Sales-support assistant | Commercial | Running | Sales-support — copper (EU) | $42.18 | 2m ago | — |
| Legal contract review | Legal IT | Running | Contract review (EU) | $11.04 | 18m ago | — |
| HR engagement bot | People Ops | Idle | Employee engagement | $0.84 | 1h ago | 1 PII |
| Market intelligence | Strategy | Stopped | Competitor monitoring (DACH) | $0 | 12m ago | KILL SWITCH |
| M365 productivity | Workplace | Running | Productivity assistant | $128.43 | 4s ago | — |
| Developer Gateway | Platform IT | Running | Coding agents (Claude · Cursor) | $76.91 | 1s ago | — |
Identity, permissions, oversight, stop, evidence.
Identity
Each agent has a runtime identity, scoped permissions, and a short-lived credential profile that flows from Mission Control to the Action Plane to the Capsule.
Permissions
What models, MCP servers, A2A peers and HTTPS endpoints the agent can reach. Bounded by the paired Gateway. Governed by use case.
Oversight
Human-in-the-loop primitives: clarification, approval, stop, rerun. All surfaced in Kosmoy Chat, all logged.
Stop controls
Pause schedules. Cancel future work. Deny new Action Plane calls. Kill switch on a live run.
Evidence
Every run links back to the approved AI use case. Tasks, runs, status changes, outputs, policy events, cost — searchable in Insights and bound to the dossier.
Module questions, answered straight.
Is Mission Control the same as the Insights Dashboard?
No. Insights is the cross-app analytics view (cost / quality / risk signals). Mission Control is the agent-fleet operational view: identity, runtime status, oversight actions, kill switch.
What's the difference between Mission Control and the Action Plane?
Mission Control is the human-facing supervision surface. The Action Plane is the runtime control plane that admits, authorizes, and audits each agent run before it executes inside a Capsule.
Does Mission Control work for agents on Foundry or Bedrock?
Inventory and status are reflected for external agents (where the upstream platform exposes it). Runtime control — kill switch, pre-flight authorization, JIT credentials — only applies to agents running in a Kosmoy Action Capsule.
Can a non-operator approve an agent action from Mission Control?
Yes. Approvals are role-scoped. End users approve their own task's bounded actions in Kosmoy Chat; operators approve in Mission Control. Both produce the same audit record.
See Mission Control in production.
Walk through the fleet view, an oversight action, and the kill switch.