Bug Recorder for AI agents

Agents read Bug Recorder at once. Changes and sends are held for a person's approval by default.

About Bug Recorder

Bug Recorder captures application errors to support server monitoring and diagnosis.

What an agent can do in Bug Recorder

Every Bug Recorder action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.

Runs at once (reads)

Looks things up in Bug Recorder without asking first. 0 actions.

None in this connector.

Held for approval by default (changes and sends)

Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 1 action.

  • Send ErrorRecord one server-side application error in Bug Recorder and trigger any notifications configured for the connected account.

Changes wait in Needs you

Changes and sends in Bug Recorder are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

How approvals work

Bug Recorder questions

Can an agent change data in Bug Recorder on its own?

Not by default. Changes and sends in Bug Recorder are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

What can an agent read in Bug Recorder?

This connector lists 0 read actions. Reads run at once, without waiting for approval.

How does Bug Recorder connect?

It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.

Bring Bug Recorder to your agents.