Claude Code on a Third-Party API: What Works and What Doesn't
As of 2026-10-08: once ANTHROPIC_BASE_URL points at a third-party endpoint such as QCode, everything the local Claude Code CLI does (chat, reading and writing files, Bash, MCP, Skills, plugins, subagents) keeps working, and auto permission mode was tested as working on 2026-10-07. Features that depend on a claude.ai account (Remote Control, voice dictation, cloud sessions, Ultrareview, the Chrome extension, Artifacts) are unavailable. This page lists each feature with the verdict, the QCode docs wording and the Claude Code official docs wording.
Updated 2026-10-08
Four verdicts
CLI, MCP, Skills, subagents
Marked as tested in the QCode docs: claude -p returns normally and file creation succeeds. The official docs say everything that runs locally works on every provider.
Auto permission mode
Tested on 2026-10-07 with Claude Code 2.1.282 / 2.1.292: Write and Bash run, dangerous commands are blocked by the classifier; classifier requests count toward your usage.
Claude models that support 1M
The QCode docs list claude-opus-5, claude-sonnet-5, claude-fable-5 and others as supporting 1M; the official docs say that behind a gateway Claude Code gives each model it recognizes the same window as on the Anthropic API. Whether 1M is the default is described differently by the two, so go by your own session.
Remote Control, cloud sessions and more
Features that need a claude.ai sign-in are unavailable through a third-party API, and Cowork should not be counted as something you use through QCode.
The short answer
As of 2026-10-08 the rule is simple: local capabilities work, account-side services don't. The QCode docs put it this way: part of Claude Code comes from the local CLI and part from hosted services on the Anthropic account side; with a third-party API key, QCode included, the first keeps working and the second does not. The official Claude Code feature-availability page agrees: "The Claude Code CLI and everything that runs locally work on every provider." The same page lists cloud sessions, Claude Code Desktop, Ultrareview, Remote Control, the Chrome extension, voice dictation and Artifacts as requiring a claude.ai sign-in and out of reach from a third-party provider. The items worth a closer look sit on the boundary: 1M context, prompt caching, image input and auto mode work; web search, PDF and Agent Teams are not covered by the docs; the desktop app needs its own configuration.
What the official docs say about features behind a gateway
The official Claude Code docs describe a gateway set through ANTHROPIC_BASE_URL in three layers. First, availability follows the provider behind the gateway, minus what Claude Code switches off itself: "If you authenticate through an LLM gateway, feature availability matches the underlying provider the gateway forwards to, except for the features Claude Code itself turns off." Whenever ANTHROPIC_BASE_URL points at a host other than api.anthropic.com, features such as Remote Control are turned off. Second, while a gateway credential is active, requests carry that credential instead of the claude.ai subscription login, and the subscription's usage limits don't apply to them. Third, the docs state that Anthropic doesn't support connecting Claude Code to non-Claude models through any gateway.
Timeline
An earlier version of the QCode feature-availability page records that every auto mode action was rejected when going through QCode.
The QCode docs update the table: auto mode tested with Claude Code 2.1.282 / 2.1.292, Write and Bash run, dangerous commands are blocked by the classifier, and the old result no longer reproduces on the new versions.
This page was checked line by line against the QCode docs and the official Claude Code docs. Claude Code ships weekly; if you see behavior that differs from this page, trust your own test.
What works vs what is limited or unverified
Works through QCode (checked 2026-10-08)
Each item below can be checked word for word in the QCode docs: first, the CLI core (chat, reading and writing files, Bash, MCP, Skills, Plugins, subagents), marked as tested, with claude -p returning normally and file creation succeeding; second, bypassPermissions mode, tested with the same task written to disk, while acceptEdits, manual, plan and dontAsk are inferred to work because they are local decision logic; third, auto mode, tested as working on 2026-10-07; fourth, 1M context on the Claude models that support it (the QCode docs and the official docs differ on whether it is on by default); fifth, prompt caching, applied automatically, with unit prices on /models; sixth, image input, with claude-opus-5 and claude-sonnet-5 as the vision models; seventh, the VS Code extension (gateway variables go in claudeCode.environmentVariables, per the official docs).
Unavailable, limited or unverified
Unavailable (they depend on a claude.ai account): Remote Control, voice dictation, cloud sessions including Claude Code on the web and mobile, claude ultrareview, claude setup-token, the Chrome extension, Artifacts and self-hosted environments. Not counted as a QCode use: Cowork. Not verified (not covered by the docs, so don't plan a purchase around them): the WebSearch tool, PDF input, Agent Teams, and how Claude Code Desktop actually behaves through QCode. One more inconsistency: whether 1M context is on by default or must be switched on is described differently in the QCode docs and the official docs, so go by what your own session shows.
Local capabilities vs account-side services
Local CLI capabilities: work
Chat, reading and writing files, Bash, MCP servers, Skills, plugins and subagents all run on your machine. The official feature table lists the CLI, the VS Code and JetBrains extensions, subagents, hooks, commands, skills, CLAUDE.md, plugins and MCP as available on every provider. Two details differ: connectors from claude.ai load only when your claude.ai subscription is the active authentication method, and MCP tool search is off by default when ANTHROPIC_BASE_URL points to a non-first-party host.
claude.ai account-side services: don't work
Cloud sessions and mobile, Remote Control, voice dictation, Ultrareview, the Chrome extension and Artifacts all need a claude.ai sign-in. The official docs say Remote Control and voice dictation are unavailable while ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN or an apiKeyHelper is active, and Remote Control is also disabled while ANTHROPIC_BASE_URL points at a non-Anthropic host. The official way to get them back is to log in with claude.ai and unset the gateway variables they check.
Feature-by-feature table (checked 2026-10-08)
Each row reads: feature → through QCode → basis in the QCode docs → official docs. ① 1M context → works on supported models → QCode environment page: 1M is supported on claude-opus-5, claude-sonnet-5, claude-fable-5, claude-opus-4-8 and claude-sonnet-4-6 → official: behind a gateway Claude Code gives each model it recognizes the same window as on the Anthropic API, and Sonnet 5 and later and Opus 4.7 and later get 1M directly; Claude Code can't detect a lower limit enforced on the gateway side. ② Prompt caching → works → QCode: caching applies automatically and the Claude family supports it; unit prices on /models → official: the gateway must forward cache_control unchanged, otherwise there is no error but every turn bills as uncached input. ③ WebSearch → unverified → not in the QCode table → official: WebSearch runs queries against Anthropic's web search backend, and behind a gateway availability depends on the provider the gateway forwards to. ④ MCP servers → work → QCode: tested as part of the CLI core row → official: available on every provider; claude.ai connectors need a subscription sign-in, and tool search is off by default. ⑤ Subagents → work → QCode: tested in the same row → official: available on every provider. ⑥ Agent Teams → unverified → not in the QCode table → official: experimental and disabled by default; enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. ⑦ Image input → works → QCode: a Claude Code session has three ways to give the model an image, with claude-opus-5 and claude-sonnet-5 as the vision models → official: vision and PDF input are model capabilities and work on every provider that offers the model. ⑧ PDF → unverified → not listed separately in the QCode docs → official: as above. ⑨ Auto permission mode → works → QCode: tested on 2026-10-07 with 2.1.282 / 2.1.292, Write and Bash run, dangerous commands are blocked by the classifier, and classifier requests count toward your usage; an English notice containing "isn't compatible" may appear at the start of a session and goes away with CLAUDE_CODE_AUTO_MODE_SERVER=0 → official: behind a gateway Claude Code asks the server for review by default, and when the gateway drops the review it falls back to its own classifier requests; CLAUDE_CODE_AUTO_MODE_SERVER=0 makes it use its own classifier requests from the start. ⑩ /usage subscription limits → not applicable → QCode: check usage on the dashboard's usage statistics page, priced from qcode.cc/models and more accurate than the CLI display → official: /usage shows session cost, plan usage limits and activity stats, and /cost is an alias; while a gateway credential is active, the subscription's usage limits don't apply. ⑪ Claude Code Desktop → untested, needs separate setup → marked untested in the QCode table → official: the desktop app reads its gateway from its own third-party inference configuration, not from ANTHROPIC_BASE_URL or settings.json, and runs local sessions only in gateway mode. ⑫ VS Code extension → works → QCode: point the extension's environment variable at https://api.qcode.cc/api → official: the VS Code and JetBrains extensions work on every provider; put the gateway variables in claudeCode.environmentVariables. ⑬ Cowork → not counted as a QCode use → QCode: treat Cowork according to your Claude plan and organization settings and do not count it as part of your QCode usage → the QCode docs add that the official gateway docs never mention Cowork. ⑭ Remote Control, voice dictation, cloud sessions, Ultrareview, the Chrome extension, Artifacts → unavailable → QCode: tested, quoting the official docs, or inferred (the Chrome extension and Artifacts are inferred) → official: they need a claude.ai sign-in and are out of reach from a third-party provider.
How to set it up on QCode
Per the QCode docs, Claude Code needs two environment variables: ANTHROPIC_BASE_URL set to https://api.qcode.cc/api, and ANTHROPIC_AUTH_TOKEN set to the cr_ key you create in the console. For auto mode, add CLAUDE_CODE_AUTO_MODE_SERVER=0 (the QCode one-click setup script has written it automatically since 2026-10-07). Then run claude -p "reply with exactly: OK"; if it returns OK, you are connected. Claude models only go through this Anthropic-protocol endpoint, and claude-sonnet-5-5, claude-opus-5-5, claude-sonnet-5 and other models switch under the same key by changing the model field. Billing is per token; unit prices for each model are on /models.
Frequently asked questions
Which Claude Code features don't work through a proxy or third-party API?
The ones that depend on a claude.ai account: Remote Control, voice dictation, cloud sessions (including Claude Code on the web and mobile), Ultrareview, claude setup-token, the Chrome extension and Artifacts. As of 2026-10-08 the QCode docs mark each of them unavailable, based on tests, the official docs or inference (inference for the Chrome extension and Artifacts), and the official feature table lists all of them except setup-token as requiring a claude.ai sign-in and out of reach from a third-party provider. Don't count Cowork as part of your QCode usage either.
Does auto mode work through QCode?
Yes. The QCode docs record a test on 2026-10-07 with Claude Code 2.1.282 / 2.1.292: Write and Bash run, and dangerous commands such as uploading a private key, deleting a directory outside the working directory, or downloading and directly executing a remote script are blocked by the classifier. Classifier requests count toward your usage; reading files, searching and edits inside the working directory skip the classifier. An English notice containing "isn't compatible" may appear at the start of a session; it disappears once you set CLAUDE_CODE_AUTO_MODE_SERVER=0. If the model you use doesn't support auto (Haiku, for example), Claude Code falls back to manual mode.
Can I use 1M context through QCode?
Yes, on models that support 1M. The QCode docs list claude-opus-5, claude-sonnet-5, claude-fable-5, claude-opus-4-8 and claude-sonnet-4-6. The official docs say that behind a gateway Claude Code gives each model it recognizes the same window as on the Anthropic API: Sonnet 5 and later and Opus 4.7 and later get 1M with no [1m] variant to select, while Sonnet 4.6 reaches 1M only through its [1m] variant. The two sources describe the default window differently (the QCode docs say the default is 200K and 1M is an opt-in switch), so go by what your own session shows.
Will /usage show my subscription limits?
Requests through QCode are not subject to your subscription's usage limits, so check QCode usage on the dashboard's usage statistics page. The official docs say that while a gateway credential is active, requests carry that credential instead of the claude.ai subscription login, and the subscription's usage limits don't apply to them. Officially, /usage (with /cost as its alias) shows session cost, plan usage limits and activity stats; the QCode docs recommend the dashboard's usage statistics page for request counts and cost details, which is priced from qcode.cc/models and more accurate than the CLI display.
Do Claude Code Desktop and the VS Code extension work with QCode?
The VS Code extension does; the desktop app needs its own configuration and has not been tested by QCode. The official feature table lists the VS Code and JetBrains extensions as available on every provider, with the gateway variables placed in claudeCode.environmentVariables in your VS Code user settings, and the QCode docs point the extension's environment variable at https://api.qcode.cc/api. The desktop app doesn't read ANTHROPIC_BASE_URL or settings.json; you enter the gateway in the app's own third-party inference configuration, and it then runs local sessions only. The QCode feature table marks Claude Code Desktop as untested.
Do web search, PDF and Agent Teams work?
Not verified as of 2026-10-08, so don't plan a purchase on the assumption that they do. The QCode feature table doesn't list these three. The official docs say WebSearch runs against Anthropic's web search backend and, behind a gateway, depends on the provider the gateway forwards to; PDF input is a model capability; Agent Teams is experimental and disabled by default, enabled with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. If any of them matters to you, test it once with your own key.
Sources
QCode docs: the Claude Code feature availability page on docs.qcode.cc (version updated 2026-10-07, all five languages, fetched 2026-10-08), plus the environment variables, endpoints and API paths, image input, context management, cost optimization, billing, FAQ, Claude Desktop and VS Code pages (fetched the same day). Official Claude Code docs on code.claude.com (fetched 2026-10-08): Feature availability, Other LLM gateways, Connect Claude Code to an LLM gateway, Gateway compatibility guide, Model configuration, Permission modes, Environment variables, Tools reference, Agent teams and Commands.
Test the features you care about with one key
Set Claude Code's ANTHROPIC_BASE_URL to https://api.qcode.cc/api to connect; billed per token, with unit prices for each model on /models.
Related reading
Claude Code auto mode: turn it off, permission modes explained
How to switch auto mode on and off, and how the permission modes differ.
Claude Code 1M context behind a gateway: /autocompact 200k
Using 1M context through a custom endpoint, and how to set the compaction threshold.
ANTHROPIC_BASE_URL and AUTH_TOKEN setup guide
The two environment variables that point Claude Code at a custom endpoint.
This page was checked on 2026-10-08; the live versions of the official Claude Code docs and the QCode docs take precedence. Claude Code ships weekly and feature boundaries can change at any time; upstream changes may happen without notice. "Tested" refers to test results recorded in the QCode docs and is not a promise about your specific setup. Model availability is whatever /models shows.