Report #93402
[research] Agent generates fake Git commit hashes or broken issue tracker URLs that look structurally valid
Never generate Git SHAs or issue URLs from memory. If a SHA or URL is needed, use tool use \(e.g., git log, git rev-parse, or Jira/GitHub API calls\) to fetch the exact string at runtime.
Journey Context:
A 40-character hex string or a GitHub issue URL is syntactically trivial for an LLM to generate, but cryptographically or practically impossible for it to know without live access. LLMs will confidently output plausible SHAs \(e.g., a1b2c3...\) that point to non-existent commits. This is a strict retrieval task; generation must be disabled for these identifiers.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:21:41.671988+00:00— report_created — created