Change Log
Review every configuration change made to your agent — by you or the agent itself — with full before/after values, actor attribution, and timestamps.
Tip: The Change Log is your agent's built-in audit trail. Every settings edit, scheduled job tweak, or mail/voice configuration change is captured automatically — with the exact before and after values.
Overview
The Change Log is a complete audit trail of every configuration change made to your agent. Unlike Runs — which tracks execution — the Change Log tracks mutations: what was changed, when, by whom, and exactly what the values were before and after.
Every time your agent updates its own settings via settings_manager, or a team member edits configuration through the UI, a change entry is recorded. This gives you a transparent, reviewable history of how your agent has evolved over time.
Where to Find It
The Change Log lives inside the History tab as a sub-tab next to Runs. Both views share a toolbar row so you can switch between execution history and configuration history without losing context.
- Runs — What the agent did
- Changes — What the agent became
What Gets Tracked
The Change Log captures mutations across four configuration surfaces:
| Category | Examples |
|---|---|
| Agent Settings | Title, persona name, description, working hours, sandbox mode, default model, cache strategy, context memory, auto-save actions, queue interval, max items per run |
| Mail Settings | Whitelist entries, whitelist enforcement, auto-queue incoming emails, email processing instructions |
| Voice Settings | Phone numbers, allowed models, voice processing instructions |
| Scheduled Jobs | Creation, updates (name, prompt, cron expression, enabled state), and deletion |
Only fields that actually changed are recorded — no-op saves don't clutter the log.
Anatomy of a Change Entry
Each entry is rendered as a card on a vertical timeline (commit-rail style), containing:
- Operation icon — Color-coded by entity type (settings, mail, voice, scheduled job)
- Entity name — What was changed (e.g., "Agent Settings", "Scheduled Job: Daily Digest")
- Operation badge — Created, Updated, or Deleted
- Actor badge — Who made the change (agent, user, or system)
- Inline preview — For single-field updates, shows the before → after values directly on the card
- Relative timestamp — e.g., "3 minutes ago", with the exact time on hover
Click any entry to open the full detail drawer.
Operations
| Operation | Meaning | Visual |
|---|---|---|
| Create | A new entity was added (e.g., new scheduled job) | Green accent, "Created" badge |
| Update | An existing entity was modified | Neutral accent, field-level diff inline |
| Delete | An entity was removed | Red accent, "Deleted" badge |
Actors
Every change is attributed to one of three actor types, so you can always tell who made a change:
| Actor | Who It Is | When You'll See It |
|---|---|---|
| Agent | The AI itself, acting through the settings_manager tool | When your agent self-configures during onboarding, or when you tell it to change something in chat |
| User | A team member editing via the UI | When someone opens Settings, Mail, Voice, or Schedule and saves a change |
| System | An automated platform action | Rare — e.g., migrations or backfills |
Agent-driven entries link to the chat session and run where the change originated, so you can trace a setting change back to the exact conversation that caused it.
Filtering
The toolbar in the top-right of the Changes sub-tab lets you narrow the timeline by category:
- All changes (default)
- Agent settings — Title, persona, sandbox, working hours, chat, actions, queue
- Mail & Voice — Channel-specific configuration and processing instructions
- Scheduled jobs — Create, update, delete on time-based triggers
Filters work alongside the grouping — filtered entries still cluster under their date headers.
The Change Detail Drawer
Clicking any entry opens a side drawer showing the full field-by-field diff for that change:
- Every modified field listed with its before and after values
- Multi-line strings (like
email_processing_instructionsor a scheduled job prompt) rendered in full — no truncation - JSON/object fields pretty-printed for readability
- Actor details (name, email, session, run) with links back to the originating chat and run
This is especially useful for verifying agent-made changes to long-form settings like processing instructions — you can see the exact text the agent wrote, character-for-character.
Grouping & Timeline
Entries are grouped by date for easy scanning:
- Today — Changes from today
- Yesterday — Changes from yesterday
- This week — Changes from the last 7 days (excluding today/yesterday)
- Older — Grouped by calendar date (e.g., "April 12")
Within each group, entries appear chronologically (newest first) along a connected commit-rail — making it visually clear which changes happened close together.
Retention
Change log entries are preserved for the lifetime of the agent. There is no automatic deletion or retention window — you can always review the complete history, even for configuration changes made months ago. Entries are only removed if the agent itself is deleted.
Use Cases
Debug Unexpected Behavior
When your agent starts behaving differently, the Change Log is the first place to look. "It was working yesterday" becomes "it was working yesterday, and here's exactly what changed overnight."
Verify Agent-Made Changes
When you tell your agent to update a setting in chat, open the Change Log afterward to confirm it did exactly what you asked — and nothing more. The inline before/after preview makes verification instant.
Audit & Accountability
For team-managed agents, the Change Log provides a clear accountability trail: who changed what, when, and why (via linked chat sessions for agent-initiated changes).
Safe Experimentation
Try an experimental setting, watch how the agent behaves, then use the Change Log to see the exact previous value and revert precisely. No guesswork about what the "original" was.
Tips & Best Practices
- Check the Change Log after onboarding — See exactly what your agent configured for itself during the first conversation
- Use the Mail & Voice filter when debugging channel-specific behavior — narrows the timeline to communication settings only
- Open the detail drawer for long text fields — The inline preview is compact; the drawer shows the full before/after for instructions, prompts, and other multi-line content
- Trace agent decisions — Agent-initiated entries link back to the originating chat session, so you can see the conversation that led to a change
- Pair with Runs — A surprising run result often correlates with a recent configuration change. Sibling sub-tabs make side-by-side investigation easy
What's Next?
- Runs & Scheduling — The other half of History — execution tracking
- Agent Settings — The main surface that feeds Change Log entries
- Mail — Mail configuration changes tracked here
- Schedule — Scheduled job create/update/delete changes tracked here