Splitkick Docs

English

Deutsch

English

Deutsch

Appearance

Several Claude accounts Beta ​

You can use more than one Claude account in Splitkick, for example a personal and a work account. Each account is its own Claude config folder with its own login.

This is a proof of concept since Splitkick 1.5.1. Some controls are still missing; see Limits.

Set up the accounts ​

Open Settings → Claude → Accounts.

  • The first row is the root install: your normal Claude login in ~/.claude. You can give it a label, for example "Personal".
  • Add more accounts in the last row. Type a label (for example "Work") and a folder (for example ~/.claude-work), then click Add account.
  • Each account has its own login status and its own Login button (Relogin when it is logged in).
  • Make active makes an account the active one. Remove removes an extra account.

Settings, Claude page, Accounts section: the root install labelled Personal and a second account Work in the folder ~/.claude-work, both logged in, Work marked active, with a row to add another account.

Settings → Claude → Accounts lists the root install with its label and every extra account with its config folder, login status, Login or Relogin button and the active marker (demo data).

The active account ​

One account is active. Every new Claude run uses it. This includes magic prompts (for example commit messages, pull requests and reviews) and the login check.

Sessions keep their account ​

A session remembers the account of its first run. Its next messages use that account, also when you made another account active.

  • Resume, fork and move keep the account. The reason: the Claude conversation is only in the folder of that account.
  • Sessions from before you set up accounts stay on the root install.
  • A transfer to another machine does not keep the account.

When you remove an account, its sessions go back to the root install. Splitkick then replays their history, because the conversation is not in the root folder. The folder of the removed account stays on disk.

Usage per account ​

Settings → Usage shows the limits of every Claude account, under its label and email. The active account is marked.

Settings, Usage page, Claude section: separate session, weekly and Sonnet limits for the Personal account and for the active Work account, each with its email and plan.

Settings → Usage shows the limits of every Claude account under its label and email (demo data).

Agents get the same data with the MCP tool get_usage. It returns every account as claude_accounts, with its label, whether it is active, and its usage or an error. See MCP server.

MCP servers, plugins and skills ​

Each config folder has its own MCP servers, plugins, skills and settings. Claude loads the ones of the account that runs the session.

The MCP server list in Splitkick (Settings and the chat toggles) still shows the servers of the root install.

Limits ​

  • You cannot pick an account per session or per project yet. New sessions use the active account.
  • Login for an extra account is not offered on native Windows. In WSL mode only the root install works.
  • Resume in terminal and the session list of the Claude CLI still use the root install.

"No conversation found" ​

The Claude CLI answers "No conversation found with session ID: …" when it looks for a conversation in the wrong config folder. Each conversation is only in the folder of the account that started it.

You can see this when you resume a session of an extra account in a terminal with plain claude --resume. That command uses the root install. To resume it there, set the environment variable CLAUDE_CONFIG_DIR to the full path of the account's folder first.