AI agents can act, not just read

Your AI agents can now do real work in Firefight, not just look things up. Ask an agent to update a runbook after an incident, fix who owns a service, or tighten an alert routing rule, and it makes the change itself, with the same permissions and approvals as everyone else.

Twelve write tools. An agent with the right permission can maintain the catalogue (upsert_catalog_entry, delete_catalog_entry), manage alert routing (upsert_routing_rule, delete_routing_rule, update_routing_config), write runbooks (upsert_runbook), attach one to an incident (attach_runbook), shape what responders are asked (upsert_custom_field, upsert_form_field), hand out incident roles (assign_incident_role), and work the approvals queue (approve_approval, deny_approval).

Slugs, not IDs. Everything is addressable by name. An agent can set which team owns a service, or gate a form field on the affected service being checkout, without ever looking up an internal ID.

OAuth for interactive clients. Clients like Claude Code connect with one command and no token handling. The consent screen names the client asking for access and the workspace it would reach, and if you belong to several workspaces you pick one right there. Native desktop clients are supported too.

Governed like everyone else. What an agent may change depends on the credential it connected with. OAuth connections act as you, service keys hold only explicit grants, and every call lands in Developer → Activity.