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

# Claude Code

> Configure official direct access, a third-party proxy, local settings.json, or CLI login for Claude Code.

Claude Code is the most complete runtime: four modes, MCP, Skills, plan approval, and the full permission dialogs all go through it.

Install the Claude Agent SDK in **Settings → SDK dependencies** first, then configure a provider.

<img src="https://mintcdn.com/mossx-docs/kz4nt5KFSKzkAZwe/images/jetbrains/provider-claude.png?fit=max&auto=format&n=kz4nt5KFSKzkAZwe&q=85&s=883c87be67be7814ac8f3c2ecd02488c" alt="Claude provider page" width="100%" data-path="images/jetbrains/provider-claude.png" />

## Four ways to connect

### 1. Add a provider (most common)

Click **Add provider** and fill in:

* Provider name
* API key
* Request URL (official direct access is fixed to `https://api.anthropic.com`)
* Optional: primary model, Haiku / Sonnet / Opus mapping, custom models

There is a visual form and a JSON editor.

Official direct access sends requests to Anthropic. A third-party preset immediately routes them to that proxy endpoint.

Built-in presets include Zhipu GLM, Kimi, DeepSeek, MiniMax, Xiaomi MiMo, Alibaba Qwen, OpenRouter, Bailian, LongCat, OpenCode Go, and others. After you pick a preset, you still enter your own key.

<Note>
  These settings stay on your computer. The plugin does not upload keys to a CC GUI server.
</Note>

### 2. Use local settings.json

Use this if you already maintain `~/.claude/settings.json`.

* The plugin does **not** read this file by default
* It reads only after you click **Authorize and enable**
* The plugin does not modify the file
* You can revoke access at any time. After you revoke it, Claude stays disabled until you enable another provider

### 3. Use CLI login

Use this for a Claude subscription account:

1. Sign in to the Claude CLI in a system terminal and confirm you can ask a question
2. Keep `env` empty in `~/.claude/settings.json`
3. In CC GUI, authorize **Use CLI login**
4. Restart the IDE if needed

If that path fails, you can temporarily set local `env` to a proxy:

```json theme={null}
{
  "env": {
    "HTTP_PROXY": "http://127.0.0.1:7897",
    "HTTPS_PROXY": "http://127.0.0.1:7897"
  }
}
```

### 4. Import from another tool

The provider page can import from cc-switch or Claude Code Router. It lists new and updated items first. Confirm before it writes.

## Models

The model picker at the bottom of the input box lists models for the current provider. You can add prices in Settings so usage stats can estimate cost. You can also pin models you use often.

## Working directory and CLI override

In **Settings → General → Environment**:

* **Working directory**: relative to the project root, or an absolute path. Leave empty to use the project root
* **Claude CLI path (override)**: when set, the plugin starts that binary instead of the bundled SDK

Most people do not need the CLI override.

## Next steps

* [Provider overview](/en/jetbrains/providers/overview)
* [Detect and install](/en/jetbrains/providers/cli)
* [Run modes and permissions](/en/jetbrains/chat/modes)
* [MCP](/en/jetbrains/customize/mcp)
* [Skills](/en/jetbrains/customize/skills)