Skip to content
Clone-Me
DocsTroubleshooting

Troubleshooting

First find what you see in the table below. Then go to that section and check each item in order.

What you seeWhere to look
The console doesn't change to "Connected"The connection check doesn't change
The terminal command shows an errorThe setup command shows an error
You get 401 or invalid_tokenYou get a 401
The agent doesn't call Clone-MeThe agent doesn't call Clone-Me
The sign-in code doesn't arriveThe sign-up or sign-in code doesn't arrive

The connection check doesn't change

The console changes to "Connected" when the agent sends its first request.

  • Claude app: Make sure you selected Connect in Claude and finished with Allow on Clone-Me's page. The consent page expires after 10 minutes.
  • Claude Code: Make sure the last line of the setup command is Status: ✓ Connected. When this test request arrives, the console changes to Connected. If you see another status, read the 401 section below.
  • Codex: Run codex again, or restart the IDE extension or the desktop app. Codex connects when it starts. In Codex, check the status of cloneme with /mcp.

Then go back to the console. The console checks again as soon as you come back to the page. If it still does not change, select Check again.

The setup command shows an error

What you seeWhat to do
The claude command was not foundInstall Claude Code first. Open a new terminal and run the command again.
That is not a token starting with cm_live_Copy the token again with Copy token in the console and run the command again.
Nothing changed.The token was already set, and when the command asked whether to replace it, you typed something other than y. Run it again and press y.
You use codex inside WSL on WindowsRun the macOS·Linux command in a WSL terminal. codex in WSL does not read the Windows config files.

You get a 401

The server did not receive the token, or it refused the token.

  1. On the connection details page in the console, check that the token has not expired or been revoked.
  2. Select Issue new token on the connection details page.
  3. Run the same setup command again. When it asks whether to replace the token, press y and paste the new token.
  • If Codex shows Environment variable CLONEME_TOKEN … is not set, check that ~/.codex/.env has the CLONEME_TOKEN line, then restart Codex.
  • If your account is suspended, the server refuses all tokens. A notice shows at the top of the console.

The agent doesn't call Clone-Me

Agents call tools when the model thinks they are needed. These help:

  • Ask directly in your request, for example "Check my standards in Clone-Me before you start."
  • Add a rule such as "Before a choice that depends on my standards, check with cloneme's ask_me first" to CLAUDE.md for Claude Code or to AGENTS.md for Codex.
  • For the Claude app, check that Clone-Me is on in the conversation's + menu. Connecting the Claude app has instructions to paste into Claude's personal preferences.
  • In the console, check Call history to see whether the agent really called Clone-Me and what it received.

The sign-up or sign-in code doesn't arrive

  • Check your spam folder. The sender is the same as for the invitation email.
  • A code works for 10 minutes. If that time has passed, get a new code.
  • If you ask for codes many times in a short time, requests are limited for a while. Try again in a few minutes.

If it still doesn't work

If an error notice in the console shows a request ID, include it when you contact us. Operators cannot see the content of your memories, so they find the server records by request ID. Use Support in the console to send a request with attachments. If you have not signed up yet, use the site's contact page.

Last updated Oct 28, 2026