# Reconnecting to Valency
> Did Valency stop working for you recently? Remove the old connector and add it back, a two-minute fix on every platform.
**Did Valency stop working for you recently?** You're in the right place. This is a known issue with a quick fix.
## What happened
We recently upgraded how Valency signs you in. Connectors you set up **before this change** were configured the old way, and what you see depends on your platform:
- **ChatGPT shows a screen titled "Add Valency again"** when it tries to sign in. The old connector can't be revived; removing and re-adding is the only fix. [Jump to the ChatGPT steps](#reconnect-chatgpt).
- **Claude or a CLI asked you to sign in to Valency again out of the blue.** That's expected, once. Complete the sign-in and you should be back, with no need to remove anything. Only if sign-in loops or keeps failing, use the steps below for your platform.
- **Claude says "Authorization with Valency failed. You can check your credentials and permissions…"** First check which email you signed in with. It may not be the one your Valency account is under. Sign in again with the right email, or check your account at [app.valency.io](https://app.valency.io/). If you're confident the email is right, remove and re-add the connector using the steps below. Details in [Troubleshooting](https://docs.valency.io/help/troubleshooting.md#claude-says-authorization-with-valency-failed).
For a connector that's genuinely stuck, the fix is the same everywhere: **remove the Valency connector completely, then add it back.** A fresh connector registers the new way and just works: no ID to paste, no port to configure. During sign-in you'll see a Valency authorization screen that wasn't there before; approve it and you're done.
:::tip[This is quick]
Removing and re-adding takes about two minutes. You won't lose anything: your Valency account, history, and settings live on our side, not in the connector.
:::
## Find your platform
Jump to the steps for the app you use:
- [Claude.ai (browser)](#reconnect-claudeai)
- [Claude Desktop](#reconnect-claude-desktop)
- [Claude Code CLI](#reconnect-claude-code)
- [ChatGPT](#reconnect-chatgpt)
- [Codex CLI](#reconnect-codex-cli)
:::tip[Let your agent do it]
Using a CLI agent like Claude Code or Codex? You can also simply ask it to **"remove the Valency connector"** and let it run the removal for you. Then add it back by following the setup guide for your platform.
:::
---
## Claude.ai
**Remove it:**
1. Open your [Claude connector settings](https://claude.ai/customize/connectors).
2. Find **Valency** in the list and click it.
3. Click **Remove** (the trash / delete option) and confirm.
**Add it back:** follow the [Claude.ai setup guide](https://docs.valency.io/guides/claude.md) from the top. It's a two-step, browser-only flow.
---
## Claude Desktop
**Remove it:**
1. Open **Claude Desktop → Settings → Connectors**.
2. Find **Valency**, click it, and choose **Remove** / **Delete**. Confirm.
3. Restart Claude Desktop so the change takes effect.
**Add it back:** follow the [Claude Desktop setup guide](https://docs.valency.io/guides/claude.md#using-it-in-claude-desktop).
---
## Claude Code
If you use the Claude account connector, remove Valency from [Claude connector settings](https://claude.ai/customize/connectors). If you added a direct MCP server, list it before removing anything:
```bash
claude mcp list
```
Run `claude mcp remove --scope ` for the Valency entry shown there. New direct connections are usually named `valency`; older ones may be named `valency-mcp`. Use the scope shown for that entry, and leave unrelated servers alone.
**Add it back:** follow the [Claude Code setup guide](https://docs.valency.io/guides/claude.md#using-it-in-claude-code). If Claude Code uses your Claude account, connect Valency once through the Claude directory. If you use an API key, proxy, or another provider, add the direct remote MCP connection instead. Neither route requires the Valency plugin. If your old add command included `--callback-port`, leave it off this time.
:::note
Claude Code caches its sign-in per server. If re-adding under the same name still fails, run `/mcp` inside Claude Code, select the Valency server, and choose **Clear authentication** before signing in again.
:::
---
## ChatGPT
**Remove it:**
1. In ChatGPT, open [Plugin Settings](https://chatgpt.com/plugins#settings/Plugins).
2. Click the **three dots** next to the **Valency** plugin title, then **Delete**.
Don't see **Plugins** or **Add custom MCP server**? Check the [ChatGPT.com setup guide's troubleshooting](https://docs.valency.io/guides/chatgpt.md#troubleshooting). Custom MCP app creation can be unavailable in a particular account or workspace.
**Add it back:** follow the [ChatGPT.com setup guide](https://docs.valency.io/guides/chatgpt.md) in a browser, or the [desktop Chat guide](https://docs.valency.io/guides/chatgpt.md#chat-and-work-cloud) in ChatGPT mode. Then select the app in your current chat and ask it to list sources. If the app is still unavailable there, try a new chat.
---
## Codex CLI
**Remove a direct connection** from your terminal. Check its saved name first:
```bash
codex mcp list
```
Run `codex mcp remove ` for the Valency entry shown there. New direct connections are usually named `valency`; older ones may be named `valency-mcp`. Leave unrelated servers alone.
**Add it back:** follow the [Codex CLI setup guide](https://docs.valency.io/guides/chatgpt/codex-cli.md) to add the direct remote MCP connection and complete browser OAuth. No plugin is needed. Keep the trailing slash in the server URL; the old fixed callback-port advice no longer applies.
:::note
Codex stores its sign-in per server. If signing in still fails, use `codex mcp logout ` for the Valency entry you found above, then sign in again.
:::
---
## Gemini CLI (no longer supported)
Google retired the Gemini CLI, and Valency no longer supports it. There's nothing to reconnect to, but if you still have Valency installed there, here's how to clean it up.
1. Remove the connector:
```bash
gemini extensions uninstall valency
```
If you added Valency manually instead, open your settings file (`~/.gemini/settings.json`, or `%USERPROFILE%\.gemini\settings.json` on Windows) and delete the `valency` block under `mcpServers`.
2. Clear the cached sign-in. Open `~/.gemini/mcp-oauth-tokens.json` (`%USERPROFILE%\.gemini\mcp-oauth-tokens.json` on Windows), a JSON array of sign-in records, and delete the one whose `"serverName"` is `"valency"`, leaving the others in place.
:::caution
This file holds the cached sign-in for **every** MCP server in the Gemini CLI, so remove only the `valency` record. Don't delete the whole file, or you'll sign yourself out of all of them.
:::
**Instead of adding it back:** set Valency up in the [Antigravity CLI](https://docs.valency.io/guides/google/antigravity-cli.md), which is where Google moved Gemini CLI users.
---
## Still not working?
If it still fails after a clean remove-and-re-add, it's probably something else. Check [Troubleshooting](https://docs.valency.io/help/troubleshooting.md) or [report an issue](https://docs.valency.io/help/reporting-issues.md). Tell us which platform you're on and which step failed, and we'll help.