Claude Code accounts

Open Settings → Agents → Claude Code → Accounts to manage separate Claude Code sign-ins. Your existing native sign-in appears as Personal. Runner stores account names, folders and selections; Claude Code keeps each sign-in in its own configuration folder and credential store.

Add an account

Choose Add account, enter a name and leave the folder on Auto, or use Browse to select an existing account folder. Auto derives a folder such as ~/.claude-work from the name. Use Personal’s settings is selected by default; clear it to keep an independent setup. Choose Add and log in and complete Claude Code’s browser sign-in. An existing signed-in folder is recognized without signing in again. Runner completes initial setup for an added signed-in account so its first interactive chat opens past Claude Code’s onboarding. During sign-in, Open sign-in page reopens the page and Cancel stops the attempt.

Each account shows its sign-in status, email and any available organization or plan. An account can be signed in without a plan label.

Switch the active account

Choose Use beside a signed-in account, or select it from the Claude Code dropdown in the usage popover. The dropdown lists signed-in accounts and their weekly usage. Manage accounts… opens the Claude Code settings page. The popover and footer show the active account’s usage.

The selected account shows Active, including when it is also main; both badges appear together.

The active account applies to new direct chats, role chats, crew members, resumed chats and recovery after a restart. Running sessions keep their original account. With several accounts configured, a Claude Code pane shows its account after the title, and its side panel shows Account and the config folder.

A role or launch environment that explicitly sets CLAUDE_CONFIG_DIR keeps that pin. An explicit ~/.claude pin is distinct from the original native sign-in, which leaves the variable unset.

Resume and fork

A paused chat says which account it ran on and which active account will continue it. Resume continues the same saved conversation; switching accounts does not copy or move its history. A fork starts a separate conversation in the active account’s folder. Existing chats retain their recorded history location even after an inactive account is forgotten.

Starting a new conversation with Claude Code’s /clear uses the account running that process. After resuming a Personal conversation with Work, /clear starts a new conversation in Work’s folder, and subsequent Resume follows that new history. Selecting another active account while the process is running does not change this location.

A setup that has never added another account keeps the existing native launch, resume, fork and usage behavior, without an account chip or dropdown.

Share the main account’s configuration

Choose Use Personal’s settings on another account’s row, then confirm. The name follows your current main account. Runner shares global memory, skills, agents, commands and enabled installed plugins, plus settings and user MCP servers for new sessions. It adds individual skill links inside the account’s own skills/ directory, preserving same-named local skills, synced skills and dot-folders. New main skills become available on the next shared launch. Each account keeps its own plugin directory, cache and installed/synced state; shared plugins load from main’s install directories at launch. The row shows shared skill/plugin counts and retained local state. Existing files and links stay in place; an account with its own settings file or explicit role settings override keeps those settings.

Choose Stop using Personal’s settings in the account’s ⋯ menu to disconnect. Runner removes only links it created whose targets still match its records, including individual skill links. The real skill directory, local/synced skills and plugin state stay in place. Removing an account uses the same cleanup. Your folder, own files, sign-in and conversation history stay on disk. On Windows, sharing uses directory junctions and a memory import; it does not require enabling symbolic links.

Settings → Skills and Settings → MCP edit the main account’s configuration. Make main moves those panes, model discovery and update-channel lookup to the selected account. The promoted account’s managed links are removed and other linked accounts follow the new owner. Its own files become the shared configuration; Runner does not copy the previous owner’s files. If Runner cannot finish because a folder is inaccessible, the previous main stays selected. Restore access and choose Retry in Accounts. Accounts involved in that change wait to launch until it finishes; the pending change survives restarting Runner.

Rename, make main or remove

An account’s ⋯ menu offers Rename, Make main, Reveal in Finder (Show in Explorer on Windows) and Remove. Renaming leaves its folder unchanged. Main identifies the owner of shared configuration; changing main never changes an account’s sign-in target.

Menu labels stay on one line; long account names are shortened to fit. The main account, active account and original native account cannot be removed; hover the disabled Remove item for the reason. Removing another account forgets it in Runner and preserves its folder, files and sign-in on disk. Switch away from an active account before removing it.