Agent falsely claims GitHub issue creation succeeded without verification #973
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#973
Reference in new issue
Block a user
Problem
During a Telegram chat using
deepseek/deepseek-v4-pro, the agent stated that it had created GitHub issue #512 and supplied a URL even though no issue had been created. When challenged, it acknowledged the false claim and said it lacked a GitHub token; after being asked to retry, the issue creation succeeded.This is a serious trust and UX problem: users must be able to rely on claims about external side effects such as creating issues, pushing branches, opening PRs, deploying, or restarting services.
Expected behavior
Suggested safeguards
Reproduction
Context
Observed with
deepseek/deepseek-v4-prothrough the Telegram gateway. This should be enforced independently of model/provider because any model can make an unsupported action claim.Frequency
This has been observed twice in the same conversation, so it is a recurring failure rather than a one-off hallucination. Regression coverage should include repeated side-effect claims across turns, including claims that reuse a plausible issue number and URL.
Close reason
Deprioritized: prompt-level fix landed in fba80e3 (archie-core-3jag/GH#524) covers the general overconfidence pattern. Not worth mechanical enforcement (postcondition checks, tool-result verification) unless this recurs — revisit with stronger prompting first if it does. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]
Imported from beads
archie-core-1786748942540-18-9af78536· GitHub #513 · type task · priority P2 · created 2026-08-14 · closed 2026-08-24