Every project change is now in the audit log
October 26, 2026 · platform
Until now the audit log answered who deployed, who added a member and who created an API key. It did not tell you who edited the agent's code or who changed a setting. Both are in there now, so the log covers every change to a project.
A few examples of what you will find. Saving files in the Code tab writes source.update with the paths that were added, changed or removed, and their sizes, but never the file contents. Starting from a template writes source.seed. When a compile finishes, the platform writes build.compile_succeeded or build.compile_failed for that compile job and attributes it to whoever requested it. A changed runner, session, voice or billing setting writes a row with the keys that changed and their old and new values. A value that looks like a secret is marked as changed and never copied.
You can read the rows in the Audit log tab of a project, in the organization-wide Audit log page, and through GET /api/v1/audit-events with an optional project_id. Filter by action, actor or time range to find a single change.
Try it
- Docs: Audit log lists every action and says what is recorded for code and settings changes.
- Dashboard: open a project and choose Audit log under Manage.