Confused on setting up claude in VS code

[bingzwork]

can anyone help me about this? or send me screen shot what and where should i put port and authentication. on adminUI, i tried adding them based on my understanding but it still asking me to login when i use the claude extension in VS code already reload it many times.

is the screenshot right? or im doing it wrong?

[darekwojciechowski]

The port and token go in VS Code's settings, not the Admin UI. The Admin UI sets them on the server side; the extension needs its own matching copy.

Open VS Code settings JSON (Ctrl+Shift+P → "Preferences: Open User Settings (JSON)") and add:

"claudeCode.disableLoginPrompt": true,
"claudeCode.environmentVariables": [
  { "name": "ANTHROPIC_BASE_URL", "value": "http://localhost:8082" },
  { "name": "ANTHROPIC_AUTH_TOKEN", "value": "freecc" },
  { "name": "CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY", "value": "1" }
]

The one that stops the login prompt is claudeCode.disableLoginPrompt. Without it the extension keeps asking you to sign in no matter what the base URL says.

Two things have to match your server: the port must be the one from your fcc-server startup log (it prints something like Admin UI: http://127.0.0.1:8082/admin, so use that number, it isn't always 8082), and ANTHROPIC_AUTH_TOKEN must equal the auth token set in the Admin UI.

Then run Developer: Reload Window, not just a reload of the extension.

To confirm it worked, keep the fcc-server terminal in view and send one message from the extension. You should see the request show up in the proxy log.

[bingzwork]

so i need to add http://127.0.0.1:8082/admin instead of just 8082? ok got that one.. now about the ANTHROPIC_AUTH_TOKEN, do I get that somewhere? or AdminUI has that default? how do i get it? or do i just need to add random words in AdminUI and match it in JSON?

[darekwojciechowski]

No, drop the /admin part. ANTHROPIC_BASE_URL is just the server root:

{ "name": "ANTHROPIC_BASE_URL", "value": "http://127.0.0.1:8082" }

/admin is only the settings page you open in the browser. The proxy serves the API at the root, so with /admin on the end the extension ends up calling http://127.0.0.1:8082/admin/v1/messages and that 404s. The only thing that log line tells you is the port number.

The token is yours to pick, nothing issues it to you. In the Admin UI it's the API/CLI Auth Token field under Runtime (that's ANTHROPIC_AUTH_TOKEN), and it ships with freecc as the default. So either leave it as freecc and put freecc in your settings JSON, or type any random string there and copy the exact same string across. It's just a bearer token guarding your local proxy.

That field is masked in the UI, and changing it needs a server restart, so after you hit Apply, restart fcc-server. Then run Developer: Reload Window in VS Code.

To confirm it worked, send one message from the extension and watch the fcc-server terminal. The request should show up in the log. If you get a 401 instead, the two tokens don't match.

[bingzwork]

weird, i follow your instruction. and still ask me for login.. the port is 8082 and the token is freecc same in the adminUI.

[michaelraj-aa]

I have the same problem, please someone tell me how to solve this.