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

# Claude Code in VS Code or Cursor

> Use the official Claude Code editor extension with your existing NexusAPI user configuration.

The official Claude Code extension offers chat, diff previews, file references, and permission prompts. VS Code and Cursor use the same underlying Claude Code user configuration.

## 1. Install the official extension

First complete the [Claude Code setup](/en/tools/claude-code). In the editor's Extensions view, search for **Claude Code** and confirm that the publisher is **Anthropic**. You can also use the [official VS Code guide](https://code.claude.com/docs/en/vs-code).

<Warning>
  Similar third-party extensions may appear in search. Install the extension published by Anthropic, and do not paste API keys into a third-party settings panel.
</Warning>

## 2. Reuse the user-level NexusAPI configuration

The extension reads the same `~/.claude/settings.json` (or Windows user-profile equivalent) as the CLI. Do not duplicate the NexusAPI key in VS Code or Cursor workspace settings.

If the editor still shows a sign-in prompt:

1. Open editor settings and search for `Claude Code login`.
2. Enable **Disable Login Prompt** when applicable.
3. Fully restart the editor.

If an editor launched from the desktop does not inherit your environment, start it from a configured terminal with:

```bash theme={"system"}
code .
```

## 3. Verify with a safe request

Open Claude Code from its editor icon, Activity Bar, Command Palette, or status bar. Send a read-only test such as:

```text theme={"system"}
Explain what the current file does without modifying it.
```

Then verify one matching entry in the NexusAPI usage log.

## Troubleshooting

* Confirm the extension, editor, and Claude Code versions are current.
* Use `/status` in the integrated terminal to confirm the Base URL is `https://nexusapi.link`.
* Restart the entire editor after changing `settings.json`.
* Preserve the original error and Request ID, then use [self-check](/en/faq/self-check).

Never send a full API key, workspace secret, or private source file to support.