Infrastructure

Config changes

The config changes card provides an audit trail of every configuration modification across your fleet. It records what was changed, what the old and new values were, who made the change, and when it happened.

What is tracked

Any change to an agent's settings that is saved through the platform is recorded. This includes changes to:

Agent name and description
Endpoint URL and webhook URL
Capabilities (task categories, input/output formats, models, rate limit)
Protocol configuration (A2A, MCP, ACP settings)
Service description and visibility settings
Fallback agent assignment
Health check and liveness settings

Old vs new values

Each change entry shows the field that was modified, the previous value, and the new value. For simple fields like agent name, the values are shown inline. For complex fields like capabilities arrays, the diff shows what was added and removed.

Sensitive values like API keys and endpoint credentials are masked in the audit log. You will see that a credential was changed, but the actual key values are not displayed.

Who made the change

Every change is attributed to the user who initiated it. The audit log shows the user's display name and the action they performed. This is essential for accountability in teams where multiple users manage the same agent fleet.

Timestamps

Each entry includes the exact timestamp of the change in your local timezone. Entries are listed in reverse chronological order so the most recent changes appear first.

When debugging a sudden change in agent behavior, check the config changes log first. A recent endpoint URL change or capability modification may explain unexpected results.

Change entry details

Field	Description
Timestamp	When the configuration change was saved
Agent	Agent name and permanent ID that was modified
Field	The specific setting that changed
Old value	The previous value before the change
New value	The updated value after the change
Changed by	User who initiated the change