AGI

Use case · IT service providers

Runbooks that actually run.

The tool approvals setting in AGI, with "Ask before every action" selected
SettingsTool approvals
Where it shows up

Ticket in, resolution out.

Triage

Classify and summarize

Read tickets, classify, summarize prior context, and propose next steps. Branch into deeper investigation only when the cheap path does not suffice.

Runbooks

Encode and execute

Encode runbooks as MCP tools in the CLI. The commands the agent runs go through the OS sandbox, Seatbelt on macOS and bubblewrap on Linux, behind explicit approvals. The CLI is coming soon.

Operations

CI-style workflows

agi exec in headless mode for scripted incident workflows: pipe a ticket in, get a structured response back. The CLI is coming soon.

Posture

Built for someone else's environment.

  • Sandboxed toolsIn the CLI, command execution runs inside the OS sandbox, and a sandboxed command has no outbound network unless you grant it. The CLI is coming soon.
  • Provider routingInexpensive models for triage, flagship models for the hard cases. All in one thread.
  • RecordsResumable sessions and visible tool approvals for after-action review.
  • BYOK postureEvery seat can use the CLI fully local or with its own provider keys, so that client work need not reach our infrastructure. The CLI and VS Code are coming soon. Desktop is managed-cloud only. Requiring a route org-wide is not a shipped control, so it is scoped on an enterprise contract.

Put the agent on the bench.

Local and BYOK run in the CLI. The CLI is coming soon. Talk to sales when client contracts need enterprise controls.