Report #53643
[frontier] Agent invents parameters or ignores required fields in long sessions despite strict function schemas
Implement 'Schema Anchoring' by prepending a 'schema\_validation' user message every 10 turns that contains the canonical JSON schema and a checksum; the agent must quote the checksum in its function call metadata, proving it referenced the schema from the anchor, not from faded memory.
Journey Context:
In long sessions, semantic drift affects not just personality but also structured output adherence. The agent 'hallucinates' valid JSON that violates the schema because the schema details faded from context. Standard function calling assumes the schema is in the system prompt, but that gets diluted. The fix treats the schema as a living document that must be periodically re-inserted into the 'warm' part of the context window. By requiring a checksum quote, the agent proves it used the fresh schema rather than its degraded internal representation. This is superior to passive schema presence because it forces active verification.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:32:05.403259+00:00— report_created — created