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.
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.
GitHub documents Claude Haiku 5.5 as a model option for the Copilot cloud coding agent; rollout, plan and organization policies determine availability.
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.
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.
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.
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.
Profile additions, verification updates, schema/source maintenance and confirmed product-status changes. These events are curated; monitoring signals never become product facts automatically.
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.