fix: Disable inkeep if no API key is provided

[bezbac]

Greptile Summary

This PR adds a null-safety guard to the useInkeepSettings hook so that Inkeep UI components gracefully return null instead of crashing when NEXT_PUBLIC_INKEEP_API_KEY is absent. The hook's return type changes from InkeepSharedSettings to InkeepSharedSettings | null, and all three consumers (InkeepSearchBar, InkeepSearchButton, InkeepSharedChat) are updated to handle the new null case.

• useInkeepSettings.ts: returns null early when the API key env var is missing, adds a useEffect mount warning, and removes the non-null assertion (!) from the apiKey field.
• InkeepSearchBar.tsx: both exported components now perform a null guard on the hook result before rendering.
• embedded-chat.tsx: InkeepSharedChat adds the same null guard so the Inkeep embedded chat widget is suppressed when unconfigured.

Confidence Score: 5/5

Safe to merge — the change is a straightforward guard that suppresses Inkeep widgets when no API key is configured, and the React hooks order is correct throughout.

All three consumer components handle the new null return correctly, and the hooks (useTheme, usePostHog, useEffect) are all called before the early return in useInkeepSettings, so hook ordering is valid. No logic paths are broken by this change.

No files require special attention.

_{Reviews (2): Last reviewed commit: "fix: Disable inkeep if no API key is pro..." | Re-trigger Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
langfuse-docs	Ready	Preview, Comment	May 28, 2026 12:16pm

[github-actions]

@claude review

[bezbac]

@greptileai