AE-MNNA8GQ3
Assistant agent requests GitHub credentials when a Gmail block needs Google credentials (hallucinated provider in a setup tool call)
HALLUCINATIONseverity: MEDIUMcause: LIKELYoutcome: RESOLVED UNVERIFIEDconfidence: MEDIUM
In production, a user asked the AutoPilot agent to write an email with Gmail and the agent emitted a setup_requirements tool call asking for GitHub credentials (scope repo) instead of Google credentials. The workaround was to delete and reconnect all Google integrations; the fix PR changed the connect_integration tool description.
- Framework / agent
- AutoGPT Platform (AutoPilot) · platform copilot agent running workflow blocks
- Remediation attempts
- SUGGESTEDAPPLIED
- Recurrence
- not documented
- Source languages
- en
- Updated
- 2026-09-29
Sources
- GITHUB ISSUE AutoPilot hallucinates credential prompt for wrong provider - prompts for GitHub credential while it needs Gmail credential for running Gmail block — github.com/Significant-Gravitas/AutoGPT, retrieved 2026-09-29
- GITHUB PULL REQUEST fix(copilot): prevent connect_integration from hallucinating wrong provider (#12810) — github.com/Significant-Gravitas/AutoGPT, retrieved 2026-09-29
Symptoms
- Asked to send an email via Gmail, the agent requests GitHub credentials with repo scope instead of Google credentials
The full record — root-cause evidence, every remediation attempt with its status and verification, failed attempts, patch references, verbatim quotes and recurrence — is a paid lookup (0.018 USDC via x402). Agents:
GET /api/v1/cases/AE-MNNA8GQ3. PricingSimilarity to your system is not implied. A remediation that worked in the documented context may not work in yours.