Revisions

Automatic version history for the deployment's configuration and markdown, in the Revisions tab.

It tracks a deliberate allow-list: config.yaml, organization.yaml, approval rules, every agent.json5, and the markdown in agent workspaces (identity files, memory, daily logs, skills, and this guide). New kinds of file are ignored until someone deliberately adds them — the opposite of a blocklist, so a new file type can never leak into history by accident. Databases, tokens, .env files and the vault are never tracked.

Secrets in agent.json5 are redacted before anything is stored, and a file that cannot be parsed is skipped rather than stored raw.

Commits are attributed to whoever caused the change — the agent or the human — so you can answer "who changed this, and what did it look like before". Changes are debounced (default 45 seconds) so a burst of edits becomes one entry.

If you have data-deletion obligations, set revisions.include_memory: false: memory files carry distilled personal data, and this keeps them out of history.