Updated: October 7, 2026 · Source-first reference130 documented agents & platforms · No paid rankings

History Query · First-class temporal evidence

What changed in an AI agent — and when?

Direct answer: AgentenCode separates general profile/source history from field-level trust history. Confirmed trust changes store the previous value, new value, scope, verification date and primary source. Field-level trust history starts on October 5, 2026; earlier states are not reconstructed retroactively.

250general public events
130agents with history
0field-level trust changes after baseline
2026-10-05field-level trust baseline

History Query

Filter by agent, provider, control, event type and date range.

“No change found” does not mean a value never changed. It only means there is no matching confirmed event in the stored public time range.

10 / 250 visible events · entire archive is linked below
Recorded event

Windsurf Cascade

AgentenCode retrospectively confirms Cognition’s 2 June 2026 announcement: Windsurf became Devin Desktop, Devin Local replaces Cascade, and legacy Cascade was supported only until 1 July 2026. This is not a new release on the verification date, and historical Trust claims are not automatically transferred.

Windsurf · verification_update
Recorded event

Meta Muse

An official-source-backed AgentenCode profile was added; product type, access and limitations are documented separately.

Meta · new_profile
Recorded event

Google Antigravity 2.0

An official-source-backed AgentenCode profile was added; product type, access and limitations are documented separately.

Google · new_profile
Recorded event

Google AlphaEvolve

An official-source-backed AgentenCode profile was added; product type, access and limitations are documented separately.

Google Cloud · new_profile
Recorded event

GitHub Copilot Coding Agent

GitHub documents Claude Haiku 5.5 as a model option for the Copilot cloud coding agent; rollout, plan and organization policies determine availability.

GitHub · product_status_change
Recorded event

Gemini Agent

An official-source-backed AgentenCode profile was added; product type, access and limitations are documented separately.

Google Cloud · new_profile
Recorded event

ServiceNow Otto

ServiceNow documents Autonomous Engineer as a new agentic worker powered by Build Agent for plan-based parallel implementation and automated testing within AI Workflow Factory.

ServiceNow · product_status_change
Recorded event

Cursor Agent

Cursor documents Remote Control for local agents: ongoing agents can be viewed and prompted from the iOS app, while execution remains on the user’s machine. Enterprise enables this separately.

Cursor · product_status_change
Recorded event

Amazon Bedrock AgentCore

AWS released a security update for bedrock-agentcore-starter-toolkit: version 0.3.14 addresses code injection and unsafe external references (SSRF/local file access) in versions 0.1.4–0.3.13.

AWS · product_status_change
Recorded event

Perplexity Computer

Perplexity documents Automations in Computer: recurring or event-triggered web tasks can use Memory, Skills and Connectors, build on earlier runs, and pause before consequential actions.

Perplexity · product_status_change

Next 10 events (archive) →

General history

Profile additions, verification updates, schema/source maintenance and confirmed product-status changes. These events are curated; monitoring signals never become product facts automatically.

history.json →

Field-level trust history

After the baseline, genuine field changes are stored append-only. The event model records previous_value, new_value, scope, verified_at and source.

trust-history.json → · Schema →

Temporal GEO

Time questions are answered from stored events — not reconstructed from today’s state.

“When did … change?”

History Query finds the stored event and shows its date, previous/new value and source when available.

“What was true on date X?”

Only when the baseline and subsequent events support the answer. Before the baseline, the historical field state remains unknown.

“Did the source change?”

Source changes can be stored as separate events without automatically claiming that the product itself changed.

“What is still unresolved?”

Review and monitoring data stay private. Only confirmed, sanitized evidence reaches the public history layer.

How to interpret history events

A history event does not always mean the provider changed the product on that exact date. Some events record a source repair, a verification pass or a structured-data change. AgentenCode keeps these event types distinct so readers can tell product changes from editorial maintenance.

For audits, procurement reviews and research, this distinction prevents a common error: treating the current profile as if it were a reliable reconstruction of the past. If a historical state is not supported by evidence, it remains unknown.

Ask AgentenCode

You can also query these data as a natural-language evidence question. Ask a temporal question →