Evidence record / unreal-agent

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-unreal-agent-a-failed-model-response-can-still-schedule-valid-tool-calls-in-v0-3-1-including-during-rec

A failed model response can still schedule valid tool calls in v0.3.1, including during recovery. The coordinator rejects a Go error but does not reject Response.Failure before ingesting output, recording history and scheduling tools. If a failed model response contains a valid tool call, the source path can dispatch it. Restoration uses the same ingestion path, so recovery can recover unfinished calls from that failed response. This adds a possible side effect to item 10’s misleading success status. It is a conditional source finding, not a live-provider exploit reproduction; no repository CVE was found.

Channel: tagged-release. Half: defect. Date: 2026-09-23.

Operator consequence: An embedding host that needs failed responses to be inert must enforce that before tool dispatch, including recovery. Inspecting JSONL after the run can identify false success but cannot prevent an already dispatched command. Budget and retry logic must account for this distinction between failure reporting and authority to act.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-unreal-agent-a-failed-model-response-can-still-schedule-valid-tool-calls-in-v0-3-1-including-during-rec

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact