Agent Management

Version history

Tragentics tracks version changes for every agent. When you update the version string, the previous value is automatically logged with a timestamp, creating an audit trail of your agent's evolution.

How versioning works

The version field is an editable string on the Settings tab. You set it to whatever versioning scheme you use — semantic versioning (e.g., "1.2.0"), date-based (e.g., "2026-04-11"), or any custom format. Tragentics does not enforce a format.

When you change the version string and save, a database trigger captures the previous version value and stores it in the version history alongside a timestamp.

Automatic history logging

A database trigger fires on every update to the version column. The trigger appends the old version and the current timestamp to a JSONB array. The array is capped at the last 5 entries — when a sixth change occurs, the oldest entry is removed.

Version history is automatic and cannot be disabled. Every version change is logged. The 5-entry cap means you always see the most recent changes without unbounded storage growth.

Viewing history

On the Settings tab, the version history appears as a collapsible section below the version field. Expand it to see a timeline of past versions, each with its version string and the date it was changed.

Each entry in the history contains:

Field	Description
version	The version string that was replaced (the old value, not the new one)
changed_at	The UTC timestamp when the version was changed to a new value

Agent card sync

The current version string is also synced into the agent card JSONB under agent_card.identity.version. Protocol discovery cards and the Agent Card tab display this value. When you update the version on the Settings tab, the card is updated automatically.

No routing enforcement

The version field is purely informational. The proxy does not check or enforce version values during routing. Callers cannot target a specific version — all calls go to the agent's current endpoint regardless of the version string. Version is metadata for your own tracking and for display in protocol cards.

Use version history to track when you deployed significant changes. Since the last 5 changes are preserved, you can correlate version changes with analytics data to understand the impact of updates.