Claude Code Personae

One Claude Code. Every backend. Point Claude Code at Anthropic, AWS Bedrock, a local model running on your own machine, or a proxy like OpenRouter — and switch in a single click.

Four ways to run Claude Code

Each combination of backend + MCP servers + allowed directories is a Preset you build once and switch between all day. Mix and match freely — "Bedrock for client work, Ollama offline, OpenRouter for niche models".

Two surfaces: pick vs. compose

The extension deliberately splits everyday use from setup:

Every VS Code Workspace inherits the Global preset by default. Picking a preset in the sidebar overrides it for that workspace only — the main panel never deals with individual workspaces.

Concept

Build presets from three types of building blocks:

• Providers — the backend (Anthropic, Bedrock, a local server, or a proxy). The provider drawer offers two top-level choices — Anthropic or 3rd party — with a curated dropdown for the rest.
• MCP Server Groups — named collections of MCP servers
• Directory Groups — additional directories Claude Code may access

A preset bundles one provider + any number of MCP server groups + any number of directory groups into a single switchable configuration.

Building blocks and presets are composed in the full editor panel:

Presets are then active at one of two scopes:

Workspaces inherit Global until you pick something else in the sidebar; Inherit from Global is one click to go back. Switching a scope's preset instantly reconfigures Claude Code — no manual file editing required.

Storage

All building blocks, presets, and scope assignments are stored in a single file:

~/.claude/coder-profiles.json

On Save All, the extension resolves the active presets and writes the resulting flat configuration into Claude Code's own files. When a workspace scope is set to Inherit from Global, any previously written workspace-level settings are cleaned up automatically.

A sample configuration is included in examples/coder-profiles.json.

Getting Started

Set up once, in the main panel:

1. Click the Claude Code Personae sparkle in the Activity Bar, then Create New Preset (or open the Command Palette → Open Claude Code Personae)
2. Create a Provider (e.g. AWS Bedrock with your profile and region)
3. Optionally create MCP Server Groups and Directory Groups
4. Create a Preset that combines your provider with any groups
5. Assign a preset to the Global Scope — the default for every workspace
6. Click Save All

Then switch as you work: open the sidebar and click a preset to use it for the current workspace (or use the status bar quick-pick).

The provider drawer has two top-level types — Anthropic and 3rd party. The 3rd-party dropdown carries presets for every supported backend (Amazon Bedrock, OpenRouter, Ollama, LM Studio, oMLX, vLLM, LiteLLM), plus an Other / Custom… escape hatch.

Anthropic Direct

• Pick Anthropic on the top selector
• Optionally set your API key in the provider editor (enter a key from console.anthropic.com, or use an op:// reference for 1Password)
• Without an API key, you'll need to run /login with an Anthropic Max or Pro plan
• Model selection is not shown — Claude Code uses its built-in defaults (Sonnet for primary, Haiku for small/fast tasks, Opus for complex tasks)

Amazon Bedrock

• Pick 3rd party, then choose Amazon Bedrock from the Provider dropdown
• Fill in your AWS profile name and region
• Pick models from the smart presets, or the picker auto-fetches your account's real models once an AWS profile is set (also available on demand via Fetch models from AWS) — newest versions first. A Region scope pill limits the list to your region's geography (US/EU/APAC/JP/AU — most restrictive selected by default), and models that share inference data with the model provider (Claude Fable/Mythos) stay hidden unless you flip Allow provider data share to Yes
• Use Mantle — flip this pill to Yes to route requests through the Bedrock Mantle endpoint (native Anthropic API shape instead of the Bedrock Invoke API). Restricts the model pickers to Mantle-format IDs (e.g. anthropic.claude-sonnet-5), clears any non-Mantle selections, and auto-selects a model per slot so the picker is never left empty
• Test models — each model slot has a Test pill that verifies profile and model access: aws bedrock-runtime converse for regular Bedrock models, or a signed request to the Mantle endpoint for Mantle-format models. Results (OK / Fail) are persisted on the provider
• Optionally set an auth-refresh command (e.g. aws sso login --profile my-profile)
• Claude Code's login/logout commands are automatically disabled when using Bedrock
• If $AWS_CONFIG_FILE is set or ~/.aws/config is a symlink, the resolved config path is shown as AWS Config (read-only). If you use easytocloud aws-envs, an AWS Env dropdown appears instead — each provider stores its own env selection in coder-profiles.json, so different providers can point to different AWS environments independently

Local models — Ollama, LM Studio, oMLX, vLLM

For when you want everything on-device. Pick 3rd party, then choose the matching entry from the Provider dropdown.

• The Base URL is pre-filled with the catalog default (http://localhost:11434 for Ollama, http://localhost:1234/v1 for LM Studio, http://localhost:8000 for oMLX/vLLM)
• Host and port stay editable — point Ollama at another machine on your LAN, or move LM Studio to a non-default port. Scheme and path are locked
• Local-only servers (Ollama, LM Studio) have no credential field at all. oMLX and vLLM accept an optional API key
• Click Fetch available models to discover models from /v1/models. Test models verifies the slot speaks Anthropic's /v1/messages API
• Standalone mode is forced on — local models never need an Anthropic login

Proxies and gateways — OpenRouter, LiteLLM

For accessing many model families through a single API.

• Pick 3rd party → OpenRouter for the public OpenRouter gateway, or LiteLLM for a self-hosted gateway
• The credential field reads OpenRouter API key (or API key for LiteLLM) — paste the value from the provider's own UI. The extension handles the rest internally
• The URL is locked to the correct scheme + path so common mistakes (missing /api, stray /v1) can't break the setup
• Standalone mode is forced on — these gateways never need an Anthropic login

Other / Custom

• Pick 3rd party → Other / Custom… for any Anthropic-compatible endpoint not in the catalog
• The Base URL is fully free-form, and a pill toggle lets you choose between API Key (x-api-key header) and Token (Authorization: Bearer)
• Standalone mode is shown as an explicit toggle and on by default — disable it only if your proxy forwards requests to Anthropic directly and you need the Anthropic login flow

"Asked to log in" even with a 3rd-party preset?

After picking a 3rd-party preset, click Save All in the panel header, then fully quit and restart VS Code (Cmd/Ctrl-Q — a window reload is not enough). Claude Code reads ~/.claude.json and ~/.claude/settings.json once at startup, so cached state from a previous session may still trigger the Anthropic OAuth login flow until the IDE process restarts. If the prompt still appears after a clean restart, re-open the panel, re-pick the preset, Save All, and quit-restart once more — that guarantees hasCompletedOnboarding: true is written and picked up.

Features

Requirements

• VS Code 1.98 or later
• For Bedrock: AWS CLI configured with a named profile (aws configure --profile <name>)
• For 3rd-party providers: a running Anthropic-compatible server (/v1/messages endpoint)
• For 1Password credentials: 1Password CLI (op) installed and signed in

Extension Settings

This extension does not add VS Code settings. All configuration is managed through ~/.claude/coder-profiles.json and resolved into Claude Code's own files on save.

Release Notes

See CHANGELOG.md.