A VS Code window with the Clauswitch picker open, showing Work, Personal and Side hustle, the pinned account named in the status bar, and no usage numbers anywhere

CLAUSWITCH · VS CODE · STATUS BAR

This window, that account.

Bind a Claude account to a VS Code window or a folder, and every Claude Code session you start there just uses it.

What this thing does

Clauswitch is a VS Code extension designed for people running multi-account Claude setups. It allows you to very quickly bind a specific Claude account to a VS Code window, pin accounts to projects, and set folder rules and global defaults that pick the right account for you.

The official Claude Code extension and any Claude Code session you launch in VS Code then pick up your choices and start with the account you chose.

Clauswitch ships a compact status bar item telling you which account is active at a glance. Hover it and a pop-up tells you why that account is active. Click it and a picker opens, where you can quickly switch accounts and set up pins.

Two clicks and you are using a different account, without the OAuth dance.

New to juggling several Claude accounts? Read our guide on how to best organize your multi-account Claude setup.

No magic, no weird patches

Claude Code keeps each login in its own config directory, and a special environment variable decides which one of these is used for new sessions. Clauswitch drives exactly this mechanism according to your rules and needs. Nothing is patched or intercepted, and there is nothing to migrate away from if you stop using Clauswitch.

Never run Claude Code on this machine? Sign in there once and Clauswitch can see the account: how to sign in to Claude Code for the first time.

What Pro adds

Every aspect of the switching functionality is free, for an unlimited number of accounts. Pro brings up-to-date usage numbers and usage credits for each of your accounts directly into VS Code.

Clauswitch Pro in a VS Code window, with session and weekly percentages beside every account in the picker, the same two numbers in the status bar, and the hover popup listing all three accounts with reset countdowns and usage credits on the two accounts that have them

Active account's usage at a glance

Work · S 10% · W 70%

The active account's session or session and weekly numbers in the status bar.

Usage overview on hover

Current usage of all your accounts

All your accounts and how they are doing. What is left, when it resets, and usage credits where they apply, without switching to find out.

Usage in the switch picker

[email protected] · Pro · S 60% · W 35% · €28.50/€50

Pick the right account for the job with all the info right there, usage credits included.

Clausage Pro included

One key · both apps

One license covers both apps in the toolkit. If you also run Clausage, the same key will activate Pro features there as well.

LAUNCH PRICE

$12, once.

One license · both apps · no subscription ·
30-day money-back guarantee

Get Pro

Where it runs

Clauswitch runs anywhere VS Code runs, on macOS, Linux, and Windows. It also works whether you use the Claude Code extension for VS Code or the claude command in the integrated terminal to interact with Claude.

Where usage numbers in Pro come from

Clauswitch always reads what Claude Code has already cached on your machine first. Only when there is nothing fresh to read does it request your usage data from the same endpoint Claude Code uses, with the token Claude Code already stores. Neither that cache nor that endpoint is ours, so we say up front what happens if Anthropic decides to remove either in the future. Read the Cutoff Clause.

Usage request frequency is designed to be gentle and stay flat even with an increasing number of accounts you track, so the usage refreshes less often per account as you add more of them. The FAQ has the details. If you run both apps from the Schizm toolkit at the same time, they share what they fetch in order to keep the total number of requests low.

Your data stays on your machine

Your usage data, and everything the extension knows about your accounts, stays on your machine, and none of it is sent to us or anywhere else. The diagnostics and analytics the extension sends exist so that we can keep improving it, and it is purely up to you whether you leave this kind of reporting enabled. The switches are in the extension's settings.