feat(providers): named provider instances (#1512 I1, #453) by currentbits · Pull Request #1516 · currentbits/solenta

currentbits · 2026-10-06T16:34:40Z

Item I1 of #1512, also #453.

What changed: you can add named instances of claude and codex, such as "Claude (work)" or "Codex (personal)", each with its own config dir (CLAUDE_CONFIG_DIR / CODEX_HOME, both verified against the real CLIs) and extra env. Instances can be picked anywhere a provider can: the model picker, Settings › Agents, agent profiles, per-project defaults (#1503) and failover chains.

How it works: a thread keeps provider (the base id) and gains providerInstance; single-string refs use claude:<id>. Every provider path resolves through the instance:

Spawn env: the instance's config dir and env are applied per spawn only. process.env is never touched, and a test proves a plain thread running beside an instance thread gets none of it.
Session resume: switching instance drops the session, because a different config dir is a different login.
Accounting: usage and quota are recorded per instance, and sign-in probes (feat: provider sign-in status with one-click Sign in; onboarding finds recent repos (#1501 G1) #1505) run under the instance env.
Sign in: the sign-in terminal carries only the config dir.
Guardrail hooks: Claude's work as-is; Codex's run through a per-thread copy of the instance home. Also fixed here: a stale auth.json link on instance switch, which would have run the next turn on the old account (tested).
Secrets: instance env is sealed like MCP server env and never logged.
Safety rules: a thread whose instance was deleted fails loudly rather than falling back to the default account. Instances are refused on remote and WSL projects.

Not covered yet:

workflow phases, automations, and skill or harness imports (these use the base default);
opencode, grok, kimi and muse;
CLAUDE_CODE_PROJECT_DIR_NAME, deliberately skipped because it would break session import.

Verified independently, on main merged with this branch:

typecheck exits 0 and vite build passes.
test:renderer: 2863 pass, 0 fail, 0 cancelled.
test:electron: 4309 pass, 0 fail, 0 cancelled.

Merge note: conflicts with #1513 (I3); I'll merge main and resolve after it lands.

🤖 Generated with Claude Code

settings.providerInstances holds extra configs of claude and codex, each with its own config folder (CLAUDE_CONFIG_DIR / CODEX_HOME) and env. Threads keep the base provider id and gain providerInstance; places that store a provider as one string use the ref <provider>:<instance>. Instance env values are sealed at rest like MCP env. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Spawn env: claude and codex children get the instance overlay per spawn, never via process.env; the kept-alive claude key includes it, so switching instance respawns. A removed instance or a remote project fails the send instead of running on the default account. Also: the codex guardrail overlay drops links into a previous home (a thread moving instance kept the old auth.json), session resume and the eject command use the instance's folder, forks keep the instance, spend is recorded per instance, the failover chain and project defaults take refs, sign-in probes and quota fetches run under each instance's env. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Settings › Agents › Providers lists each instance under its base with its own sign-in state, plus Add instance / Edit / Delete: provider, name, config folder, and env rows with masked values. The model picker shows an instance as its own group; the thread's current pick is its ref, so the fresh-session warning covers switching accounts too. Marks and colours follow the base provider. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

#453) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

chatgpt-codex-connector · 2026-10-06T16:34:48Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-06T16:39:07.305011Z	`c00e306`	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c00e3064f2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-10-06T16:39:04Z

  // patch config + provenance. sessionId stays null (fresh session).
  const forkPatch = {
    provider: nextProvider,
+    ...(nextInstance ? { providerInstance: nextInstance } : {}),


Clear the default instance when forking to a base provider

Always include providerInstance in this patch, even when nextInstance is null. If the global default is a named instance, createThread() initially assigns that instance; a fork from a base-provider thread, or an explicit handoff to another base provider, then omits this field and retains the default instance. The fork can consequently run on the wrong account or fail because its base provider and retained instance do not match.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-10-06T16:39:04Z

+    if (Object.prototype.hasOwnProperty.call(patch, "providerInstances")) {
+      this.data.settings.providerInstances = validateProviderInstances(
+        patch.providerInstances,
+      );


Invalidate sessions when an instance configuration changes

When an existing instance's config directory or account-related environment is edited, this replacement leaves every thread on that instance with its old sessionId. The next run respawns the CLI under the new configuration but passes the session ID from the previous account/config directory, causing resume failures or potentially attaching to an unrelated session with the same ID. Treat execution-affecting edits like an instance switch by clearing affected sessions, or make those fields immutable while the instance ID is retained.

Useful? React with 👍 / 👎.

# Conflicts: # electron/test/auto-settle-settings.test.js # electron/test/budget-spend.test.js

currentbits · 2026-10-06T16:46:00Z

Merged main into this branch (now includes #1513, #1514 and #1515). Resolved the expected-settings fixtures in auto-settle-settings.test.js and budget-spend.test.js: main's resumeInterruptedRuns: false plus this branch's providerInstances: [].

Verified on the merged tree:

typecheck exits 0 and vite build passes.
test:renderer: 2882 pass, 0 fail, 0 cancelled.
test:electron: 4346 pass. The 1 failure was provider-switch-context under full-suite load, a known flake that reads a half-written log file; it passes 12 of 12 alone. Fixing that test separately.

Willem and others added 5 commits October 6, 2026 18:12

Settings fixtures carry providerInstances; fork tolerates a bare store (

8ad3c93

#453) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Model pill names the instance a thread runs on (#453)

c00e306

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

chatgpt-codex-connector Bot reviewed Oct 6, 2026

View reviewed changes

Willem added 2 commits October 6, 2026 18:40

Merge remote-tracking branch 'origin/main' into i1-resolve

911180a

# Conflicts: # electron/test/auto-settle-settings.test.js # electron/test/budget-spend.test.js

Merge remote-tracking branch 'origin/main' into i1-resolve

febccb6

currentbits merged commit 3e1a578 into main Oct 6, 2026
6 checks passed

This was referenced Oct 6, 2026

Workflow round 4: provider instances, web access UX, crash auto-continue, polish #1512

Closed

Named provider instances: work/personal accounts, isolated config dirs, OpenRouter #453

Closed

Navigation Menu

Repository navigation

feat(providers): named provider instances (#1512 I1, #453) - #1516

feat(providers): named provider instances (#1512 I1, #453)#1516
currentbits merged 7 commits into
mainfrom
coder/1512-i1-named-provider-instances-1294ea

currentbits commented Oct 6, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 6, 2026 •

edited

Loading

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Oct 6, 2026

Uh oh!

chatgpt-codex-connector Bot Oct 6, 2026

Uh oh!

currentbits commented Oct 6, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

currentbits commented Oct 6, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Oct 6, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Oct 6, 2026

Choose a reason for hiding this comment

Uh oh!

currentbits commented Oct 6, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chatgpt-codex-connector Bot commented Oct 6, 2026 •

edited

Loading