Gemini Gems Disappeared? Check Your Account and Saved Work

If your Gemini Gems have disappeared, the most common causes are a plan change that removed access, a browser or cache issue hiding the interface, or a documented product update that moved or renamed the feature. Work through the checks below before assuming your Gems are gone permanently.

Whatever the cause, the practical problem is the same: standing instructions you relied on are not accessible when you need them. Tools like fenbs keep tested prompts and project context outside any one AI app, so a Gem going missing does not also mean losing the work behind it. See the Gemini Gems overview for background on what Gems are and where they normally appear.

Check your plan first

Gems require a Gemini Advanced subscription (sold as part of Google One AI Premium). If that subscription has lapsed, changed, or been moved to a different account, the Gems panel will not appear. Check your Google One membership page↗ (opens in a new tab) to confirm the subscription is active on the account you are signed in with.

On a Google Workspace account, your Gems access depends on the plan your organization has and whether your administrator has enabled the feature. If Gems worked before and suddenly stopped, contact your Workspace administrator to confirm nothing changed at the account level.

Check which account is active

If you have multiple Google accounts, Gemini may have opened on the account without an Advanced subscription. Click your profile picture in the top-right of Gemini, confirm which account is selected, and switch to the one with the active plan. Gems are tied to the account that created them, not just the plan.

This is a common cause of Gems appearing on one device and not another: one browser is signed in to the right account and the other is not.

Clear cache and try a different browser

Browser cache can hide parts of the Gemini interface. Open an incognito or private window and sign in to Gemini there. If the Gems panel appears, the issue is with your browser's cached data. Clear the cache and cookies for gemini.google.com and reload.

If incognito does not help, try a different browser altogether. If Gems appear in the second browser, a browser extension in the first may be interfering with the page.

Documented product changes to know about

From November 2026, Google is renaming Gems to skills on personal accounts. If your account is in an early rollout of that change, you will find the same feature under a new label. Look for a "skills" section where Gems used to appear, and check Google's Gemini help center↗ (opens in a new tab) for the current navigation.

Google Workspace rollouts sometimes lag personal account changes. Your colleagues on Workspace may still see "Gems" while personal accounts show "skills". The underlying feature is the same; the label depends on the account type and rollout timing.

Related: the Claude Projects vs Gemini Gems comparison covers what to check if you are considering switching to a different tool while the situation resolves.

What to do if a Gem is permanently gone

If a Gem was deleted or the account that created it is no longer accessible, the instructions cannot be recovered from Gemini. The Gem itself was a configuration saved inside Google's system, not a file you own.

If you saved the instruction text somewhere outside Gemini, you can recreate the Gem. If you did not, you will need to write new instructions from memory or start with a template. See the Gemini Gems templates guide for a set of starting points you can adapt.

Going forward, the simplest protection is to keep a copy of any instruction you spent time writing. A shared document, a note app, or a Skills record in fenbs all work. The goal is to own the text independently of whether Gemini is available.

If your Gems are shared with a team on Google Workspace and have disappeared for everyone at once, the issue is likely at the organization level: a plan change, a feature rollout, or an administrator setting. Check with your Workspace administrator rather than troubleshooting individually. A plan change that removes Gemini Advanced access affects all members at the same time, so the account and browser checks above will not help in that case.

How to do this with fenbs

1. Create a free account and open your personal kanban board.
2. Open Skills and prompts. Add a Skill for each Gem instruction you want to preserve. Paste the instruction text and name it after the task it covers.
3. Add the projects those Gems support to your board, including current tasks and any standing decisions.
4. Connect a supported AI app via Integrations so it can read your Skills and project context without needing Gemini.
5. If you rebuild a Gem later, copy the instruction text from fenbs rather than writing it again from scratch.

fenbs does not connect to Gemini directly over MCP. It connects to Claude, Claude Code, Cursor, Codex CLI, Gemini CLI, GitHub Copilot and Devin Desktop. The ai-prompts topic hub has more guides on keeping AI instructions portable.