# Claude Code Classifier Billing Notice

When you use Claude Code through QCode in the `auto` permission mode, you may see this notice:

```text
We're changing auto mode to no longer charge for classifier requests in Claude Code.

However, this session isn't eligible because your requests go through api.qcode.cc,
which isn't compatible with this update.

Nothing breaks: auto mode keeps working, and its classifier requests are billed as before.

To fix it and access the new version of auto mode, ask your gateway to implement:
https://code.claude.com/docs/en/auto-mode-classifier-billing
```

The host in the notice is the endpoint you configured (for example `api.qcode.cc` or `asia.qcode.cc`). **The notice doesn't
stop anything from working.** This page explains what it means and what you can do.

## What the notice means

Before running actions such as shell commands or network requests, `auto` mode asks a **classifier** whether the action is
safe. Anthropic is moving this check to its own servers, where it runs as part of the session's own model requests and is not
billed separately.

That server-side check isn't available through QCode at the moment, so Claude Code keeps sending its own classifier requests,
exactly as before:

- `auto` mode keeps working, and dangerous actions are still blocked;
- classifier requests still count toward your usage and appear as `claude-sonnet-5` in the dashboard. Where they come from and
  how to reduce them is in [Why Claude Sonnet 5 Appears in Your Usage](/docs/reference/why-sonnet-5-in-usage).

In other words, the change only affects sessions connected directly to the Anthropic API; sessions through QCode behave and
cost the same as before.

## What happens when the notice appears

- **Interactive sessions**: the notice **holds the first action that needs a check**. Press **Enter** to continue: that action
  and the rest of the session's checks use Claude Code's own classifier requests, and the notice doesn't reappear on that
  machine for 24 hours.
- Pressing **Esc** or **Ctrl+C** cancels that action and stops the current turn. The session stays in `auto` mode, and the
  notice appears again before the next check.
- **Non-interactive sessions** (`claude -p`): the notice is only printed to stderr; nothing waits and the session continues.

To check the current session, run `/status` in Claude Code: when the `Auto mode server` row reads `Disabled`, the session is
using Claude Code's own classifier requests.

## How to remove the notice

Set this environment variable before you start Claude Code:

```bash
export CLAUDE_CODE_AUTO_MODE_SERVER=0
```

Or add it to `env` in `~/.claude/settings.json` so it always applies:

```json
{
  "env": {
    "CLAUDE_CODE_AUTO_MODE_SERVER": "0"
  }
}
```

With the variable set, Claude Code no longer tries the server-side check first and goes straight to its own classifier
requests, so the notice doesn't appear. Behavior and billing are the same as pressing Enter. According to the official
documentation this is a temporary setting that may change in a later release.

If you set up your environment with the [One-Click Setup Script](/docs/getting-started/one-click-install), the variable is
already set. Other variables are covered in [Environment Variables](/docs/getting-started/environment).

## FAQ

**Will this never be supported?**
That isn't what we're saying. The check that isn't billed separately is performed by Anthropic's own servers inside the main
request, and using it through a third-party relay or gateway requires dedicated support; many similar services are still
working on it. We are following it closely and will update this page when there is progress.

**Does `CLAUDE_CODE_AUTO_MODE_SERVER=0` cost more?**
No. It only makes Claude Code skip the server-side attempt and stops the notice; the classifier requests are sent either way,
so the cost is the same as without it.

**Want fewer classifier requests?**
The classifier only runs in `auto` mode. Press `Shift+Tab` to switch to another permission mode; see
[Why Claude Sonnet 5 Appears in Your Usage](/docs/reference/why-sonnet-5-in-usage) and
[Permission Configuration](/docs/usage/permissions) for the details.