Skip to content

fix(memory): skip ingestion when Gemini API key is not configured#37

Open
mikekidder wants to merge 1 commit intoearlyaidopters:mainfrom
mikekidder:fix/gemini-api-key-guard
Open

fix(memory): skip ingestion when Gemini API key is not configured#37
mikekidder wants to merge 1 commit intoearlyaidopters:mainfrom
mikekidder:fix/gemini-api-key-guard

Conversation

@mikekidder
Copy link
Copy Markdown

@mikekidder mikekidder commented Apr 10, 2026

Summary

  • Adds a GOOGLE_API_KEY guard at the top of ingestConversationTurn() in src/memory-ingest.ts, so memory ingestion is silently skipped when Gemini is not configured
  • This prevents an unhandled error that would occur when the function tried to call the Gemini API without a valid key
  • A version of this fix was submitted previously but did not make it into recent builds, so this re-applies it cleanly against the current main branch

Test plan

  • Start the bot without GOOGLE_API_KEY set in .env and confirm no crashes occur during conversation
  • Start the bot with GOOGLE_API_KEY set and confirm memory ingestion still works as expected
  • Verify npm run build completes without errors

🤖 Generated with Claude Code

Prevents memory-ingest from calling Gemini when GOOGLE_API_KEY is unset,
which would throw an unhandled error for users without Gemini configured.

Note: We submitted a version of this fix previously but it appears to
have not made it into recent builds.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant