Google Workspace

Gemini Gems: Troubleshooting External Links Not Opening in New Chats

Gemini Gem External Links Not Opening? Understanding a Server-Side Bug and Its Workarounds

Google Workspace users are increasingly leveraging the power of Gemini Gems to tailor their AI interactions, creating personalized assistants for specific tasks and workflows. These custom Gems promise streamlined productivity, but a recent, reproducible technical bug has surfaced, causing frustration for users: external links, particularly YouTube links, fail to open correctly in newly created Gem chats.

This isn't a minor glitch; it's a consistent, reproducible issue affecting both the Gemini Android app and the web version at gemini.google.com. The problem points to a server-side issue rather than a client-side configuration error.

The Reproducible Bug: Links That Only Work Later

The core of the problem lies in how Gemini handles external links in a freshly initiated Gem conversation. Users describe a consistent pattern:

  1. Open a custom Gem and start a new chat.
  2. Ask the Gem a question that produces an external link (e.g., a YouTube video).
  3. Tap the link — it does not open correctly.
  4. Leave the chat.
  5. Create or open another chat so that the affected chat becomes the second item in the history list.
  6. Return to the affected chat.
  7. Tap the exact same URL again.
  8. The link now opens correctly.

Initial reports suggested a general external link issue, but diligent community testing by users like Dmytro Gumburov narrowed it down to YouTube links specifically. Various YouTube URL formats (e.g., youtube.com/watch?v=..., youtu.be/..., m.youtube.com/watch?v=...) all exhibit the same behavior. This confirms it's not a URL formatting problem but rather a specific handling issue within Gemini's session state for YouTube content.

Comparison of Gemini chat showing a broken YouTube link in a new chat versus a working link after moving the chat to history
Comparison of Gemini chat showing a broken YouTube link in a new chat versus a working link after moving the chat to history

The Technical Explanation: A Server-Side Initialization Glitch

Community experts have identified this as a server-side session initialization issue. It appears that newly created Gem threads across both web and Android platforms experience a temporary glitch in external hyperlink routing. Once the thread is no longer considered "active" or "new" and is pushed into the conversation history, its state is presumably re-initialized or updated, allowing the links to function as intended.

This behavior is crucial because it rules out client-side caching, browser settings, or device-specific configurations as the root cause. The problem originates on Google's servers, affecting the initial state of a Gem conversation.

Immediate Workarounds for Broken Links

While Google's engineering team works on a permanent fix, several temporary workarounds can help you access those crucial links:

The Conversation Switch Workaround

This is the most widely reported and effective method. When you encounter a non-opening link in a new Gem chat, simply open or create a secondary chat. This action moves the affected session down in your conversation history. Once the original chat is no longer the most recent, re-open it, and the links should now function correctly.

The Refresh Trick

Sometimes, a simple refresh can force the chat state to update. If you're on the web, try pressing F5 or reloading the page. On the Android app, force-closing and re-opening the app might achieve a similar effect, forcing the database to sync the chat state immediately.

Copy-Paste the Link

If you're in a hurry and the above methods don't immediately work, you can bypass the Gem's link handling entirely. Long-press the link (or right-click on the web) to copy the URL text directly, then paste it into a new browser tab or your preferred application. This ensures you get to the content, albeit with an extra step.

The "Dummy" Prompt

To proactively avoid the issue, start your custom Gem sessions with a quick, innocuous prompt (e.g., "Hello" or "Start"). Then, back out to the main Gemini menu and immediately return to the chat. This effectively pushes the chat into the "historical" state before you even generate any links, potentially preventing the bug from occurring with your actual queries.

Visual guide for submitting feedback in the Google Gemini Android app
Visual guide for submitting feedback in the Google Gemini Android app

Reporting the Bug: Your Role in a Faster Fix

The most effective way to accelerate a fix is to submit a detailed bug report directly to Google. Their engineering teams rely heavily on precise reproduction steps to identify and resolve server-side issues.

How to Submit a Diagnostic Bug Report

  • On Web: Open the affected chat at gemini.google.com, select Help in the bottom-left panel, click Report a problem, and paste your reproduction steps.
  • On Android: Open the Gemini app, tap your Profile icon in the top right corner, select Help & feedback, and choose Send feedback with system logs enabled.

Remember, the more detailed and consistent your reports are, the quicker Google's engineers can pinpoint and resolve the underlying server-side issue. Make sure to reference the specific URL of your affected chat if possible, and always include the exact steps you followed to reproduce the bug.

Where Workalizer Helps: Monitoring AI Tool Adoption

While this specific bug is a technical issue to be resolved by Google, Workalizer provides valuable insights for organizations leveraging Google Workspace, including the adoption and usage of AI tools like Gemini. For administrators looking to understand how their teams are utilizing Gemini and other Google Workspace applications, our How to Use the Gemini Usage Report offers a comprehensive overview. This report can help you track engagement, identify power users, and understand the overall impact of AI on productivity within your organization. Similarly, for a broader view of your Google Workspace ecosystem, the How to Use the Google Workspace Dashboard can provide a centralized hub for monitoring various application usages, including those for which you might be tracking google calendar usage or even Google Tasks usage report for specific projects.

Gemini Usage Report widget in Workalizer showing key metrics and filters.
The Gemini Usage Report widget in context with period and scope filters.
Detail view for Gemini Usage Report.
Additional context for using the Gemini Usage Report widget.
Activity Summary widget on the Workalizer dashboard showing activity grouped by time period.
The Activity Summary widget gives a quick overview of engagement across the selected period.
Meeting Activity Overview (MeetChart) on the dashboard showing meeting count and duration.
The Meeting Activity Overview shows meeting volume and duration for the selected period.

Conclusion

The reproducible bug with external links in new Gemini Gem chats is a clear server-side issue that Google is expected to address. By understanding the problem, utilizing the temporary workarounds, and diligently submitting detailed bug reports, Google Workspace users can contribute to a faster resolution and ensure their customized AI experiences remain seamless and productive. Stay informed and keep leveraging the power of Gemini, even as we navigate these minor bumps along the way.

Share:
GmailGoogle Chat

|

Google Workspace Marketplace badgeRequires Google Workspace Admin Permission
Live Demo
Employee communication analytics dashboard