Why

When attempting to use the Gmail block via AutoPilot, the system requests GitHub credentials instead of Google credentials. This causes confusion; the workaround is to delete all Google integrations and reconnect.

Reported by

Toran (torantula) 2026-04-16 in prod. Session: 73f57993-c371-4619-9b92-bbf3c4027f24

Behaviour

• User asks AutoPilot to write an email with Gmail
• AutoPilot emits a setup_requirements tool call requesting GitHub credentials (provider: github, scopes: repo) instead of Google
• User was asked to delete Google integration to fix
• Deleting all Google integrations and reconnecting resolves the issue

Root cause hypothesis

Toran: the memory prompt insert from a prior session contained GitHub credential requests, confusing the LLM into requesting GitHub creds in a Gmail context.

Pwuts: much of the content injected into the initial user prompt looks like noise/spam, likely contributing to the confusion.

Offending tool call (Langfuse trace)

Type: setup_requirements. Agent: connect_github (GitHub, provider: github, scopes: [repo]). Session: 73f57993-c371-4619-9b92-bbf3c4027f24

Related issues

• OPEN-2592: Avoid Duplicate Google Credentials
• SECRT-2091: Gmail OAuth scope mismatch
• OPEN-1857: Handle incremental/duplicate OAuth auth

Workaround

Delete all Google integrations and reconnect.