Audit Logspublic
Last verified 9 Oct 2026
DigitalOcean Harness Runtime provides managed, hardware-isolated microVM sandboxes with built-in tools such as Chromium to run harnesses and execute arbitrary code. Rich lifecycle APIs preserve conversational history and working state across sessions, letting you pause, resume, and fork work to control costs and adapt to the nonlinear nature of agentic workflows. Scale complete agents such as Claude Code or use sandboxes independently for code execution, all through the same service. See What You Can Build for example use cases.
Harness Runtime audit logs show a record of the actions taken by an agent in a session, when they took place, and who approved, rejected, or deferred them. These include built-in action types such as bash, file.read, file.write, web.fetch, and the git.* operations, as well as Action Gateway tools. Each session has an audit log, which you can view in the Control Panel. Audit log records do not expire.
Each record in the audit log contains the following:
- Tool: The name of the tool or action type the agent called.
- Decision: The result of the policy decision. For an
askdecision, the record also shows whether the action was approved, rejected, or deferred. - Actor: The person who provided input for the action when asked.
- Prompt: The prompt to the agent that led to the action. The record links back to the relevant tool and prompt in the session, so you can navigate to the exact spot where the action took place.