> ## Documentation Index
> Fetch the complete documentation index at: https://nemonist.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Fixes for the common setup problems.

> [accordion] "This Nemonist API key is not valid or is disabled"
>
> The client is sending another key. Check it is your nemonist key. For Claude Code, `ANTHROPIC_API_KEY` must be empty and you may need `/logout`. Open a new terminal after editing your shell profile.

> [accordion] "Not found" from a coding agent
>
> Agents send tools with every request, and some models take no tools. Pick a model whose page lists `tools` under **Supported parameters**, such as `anthropic/claude-sonnet-5.5` or `openai/gpt-5.5`.

> [accordion] "This model does not support custom API keys" in Cursor
>
> Cursor's own models, including its default, cannot use your key. Add a model by its ID from the [model list](https://nemonist.com/models), for example `anthropic/claude-sonnet-5.5`, and pick it. See [Cursor](https://nemonist.com/docs/clients/cursor.md).

> [accordion] "AI Model Not Found" or "Model name is not valid" in Cursor
>
> Cursor can refuse a model ID without its provider prefix (such as `claude-sonnet-5.5`) itself, before the request reaches nemonist. Add the model again exactly as the [model list](https://nemonist.com/models) writes it, for example `anthropic/claude-sonnet-5.5` rather than `claude-sonnet-5.5`, and pick that one.
>
> If the model already has its prefix and the error comes from `/summarize`, Cursor itself refuses that command for a model added under your own key; the request never reaches nemonist, and no model ID fixes it. You do not need it: Cursor still summarizes on its own when the chat fills its context ("Chat context summarized"), and you can start a new chat at any time, because nemonist's memory carries what you worked on into it.

> [accordion] "Provider Error" or "missing /api/v1" in Cursor
>
> The base URL is wrong. In **Override OpenAI Base URL**, set `https://nemonist.com/api/v1/cursor` exactly. Other clients use `https://nemonist.com/api/v1`.

> [accordion] Tool calls fail in Cursor
>
> The base URL must end in `/api/v1/cursor`, not `/api/v1`: that endpoint takes Cursor's own request format. See [Cursor](https://nemonist.com/docs/clients/cursor.md).

> [accordion] Which model IDs can I use?
>
> Any ID from the [model list](https://nemonist.com/models), written as there (`provider/model`).

> [accordion] Do I need a plugin or an SDK?
>
> No. nemonist is a drop-in endpoint: change the base URL and keep your client, tools and models.

> [accordion] Can I use my own key?
>
> Yes. Connect your Router key on the **Your key** page and requests are billed to your own account; memory and learning work the same. See [Bring your own key](https://nemonist.com/docs/concepts/byok.md).

> [accordion] My agent does not remember anything
>
> Memory belongs to the project, linked by `.nemonist/key` at its root. Check the file exists and that you are in the same project folder. A clone on another computer finds the same memory when it has the committed `.nemonist/config` and you use the same API key; without the config it starts empty. See [Memory](https://nemonist.com/docs/concepts/memory.md).

> [accordion] I deleted .nemonist/ and my notes are gone
>
> The notes are not deleted. If `.nemonist/config` is committed to git, the next chat reads it from git, recreates `.nemonist/` and reconnects the same memory; nothing else is needed (`git status` then shows `.nemonist/config` unchanged or only a trailing newline added). Otherwise the agent says the project now has a new, empty memory. If the project is in git and that happened anyway, run `git checkout -- .nemonist/config` (or restore it from your backup) and delete `.nemonist/key`: the next chat writes a key for the old memory by itself. Without the old config, open the old project on the **Memory** page (the **Possibly lost** list finds it), then **Settings**, **Lost .nemonist/key? Issue a key**, and put that key in `.nemonist/key`. If `.nemonist/key` and `.nemonist/config` name different folders, your agent asks which to keep, and `GET /memory-file` returns the key's `folder` so you can compare it with the config.

> [accordion] I copied my project and both copies share notes
>
> A copy (`cp -a`, a backup restore, a renamed folder) keeps `.nemonist/key`, so it uses the same memory as the original. The first chat in the copy is told so and asks you: keep sharing, or give the copy its own memory. Choose a separate memory (or ask your agent for one at any time): it writes a new `.nemonist/key` and `.nemonist/config` in the copy only, which nemonist issues for it, and saves your copy-only notes there. Deleting the two files yourself does not split a project whose `.nemonist/config` is committed to git: the next chat reconnects the shared memory from git.
>
> A copy made without dot-folders (a tar or zip export that skips `.nemonist/`) has no key, so its first chat creates a new, separate memory and nemonist says so at the end of that reply. To use the original's notes there, copy the original's `.nemonist/key` and `.nemonist/config` into the copy, or issue a key on the original's Memory page (**Settings**, **Issue a key**).

> [accordion] How much of my key's limit have I used?
>
> Send `curl https://nemonist.com/api/v1/key -H "Authorization: Bearer $NEMONIST_API_KEY"`: `limit_usd`, `spend_usd`, `remaining_usd` and `resets_at` are under `budgets`. No account is needed. A request refused with 402 was not charged. Only the account that issued the key can raise its limit; if someone gave you the key, ask them.

Other errors: see [Errors and retries](https://nemonist.com/docs/concepts/errors.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.