Multi-Account Login

The Blueprint AI panel uses your normal Claude account — there is no separate Blueprint AI signup. On first launch you’ll see the login screen; after a successful OAuth handshake your credentials are reused exactly as if you’d run claude in a terminal.

First-time login

Clicking Connect Claude on the login screen spawns the Claude CLI’s OAuth flow in your default browser, you sign in (or pick an existing session) on claude.ai, the browser redirects back to a confirmation page, and the panel detects the new credentials and switches to the chat view. If anything fails (browser blocked, OAuth timeout, missing CLI), the screen shows a specific diagnostic and a Retry button.

Claude Pro is required

Claude, which the panel embeds, needs a paid Claude plan (Pro or higher) or an Anthropic API key with pay-as-you-go billing. Free Claude accounts can sign in but can’t make tool calls.

The account locker

When Save Claude accounts after login is enabled (default), each successful sign-in is copied into a local locker at ~/.claude/BlueprintAI/<email>/. Each subdirectory contains a snapshot of the credentials that account would have needed to sign in fresh — its ~/.claude.json entry, the OAuth tokens, and any session cookies.

The locker is keyed by email, stays inside ~/.claude/ (never leaves the directory the Claude CLI already trusts), is read-write to the current OS user only (0700 on POSIX, ACL’d on Windows), and holds no project data — only per-account auth state. Disable persistence in Editor Preferences → Blueprint AI.

Switching, adding, signing out

When the locker has more than one account, the TopBar shows the active account email next to the history button. Clicking opens the AccountPicker:

+--------------------------------+
|  Accounts                      |
|  ● you@studio.com  (active)    |
|  ○ alt@studio.com              |
|  ○ contractor@vendor.io        |
|  --------------------------    |
|  [ + Sign in to another...]    |
|  [ Sign out current ]          |
+--------------------------------+

• Switch — selecting a row swaps the active credentials into ~/.claude.json, restarts the Claude CLI sidecar, and refreshes the SessionDrawer (each account has its own project-scoped session list). The currently active session keeps running; the swap only affects the next call.
• Add — + Sign in to another… re-runs the OAuth flow; the new credentials are added to the locker and switched in immediately. The CLI’s claude /login and claude /logout flow through the same locker.
• Sign out — Sign out current logs out and removes that account from the locker; the /logout slash command logs out without touching the locker so you can sign back in later. Signing out the last account returns the panel to the login screen at next send.

What gets stored where

Item	Location	Survives restart?
Active credentials	~/.claude.json	Yes — managed by the Claude CLI
Account locker	~/.claude/BlueprintAI/<email>/	Yes — only if Save accounts is on
Sessions (JSONL)	~/.claude/projects/<project-key>/	Yes — per project, shared across accounts
Telemetry consent	EditorPerProjectUserSettings.ini	Yes — per project, per developer
MRU mode picks	EditorPerProjectUserSettings.ini	Yes

API key instead of OAuth

If you use Claude via an API key (e.g. for a service account or pay-as-you-go), set the standard ANTHROPIC_API_KEY environment variable before launching the editor. The panel detects it and skips the OAuth flow entirely — no locker entry is created.