Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Feature Request: Per-workspace account/subscription binding in Conductor [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46090•Fetched 2026-04-11 06:29:14
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Author
FranzFelbererFranzFelberer
Participants
FranzFelbererFranzFelberer
Timeline (top)
labeled ×4closed ×1commented ×1

Fix Action

Fix / Workaround

Current workarounds (all inadequate)

WorkaroundWhy it doesn't work
Set ANTHROPIC_API_KEY per workspace in project settingsBills at pay-per-use API rates, not against the Max subscription — significantly more expensive
claude logout / claude login hook on workspace switchBreaks all other running workspaces that share the session
Run two Conductor app instancesUnsupported, fragile, no way to direct workspaces to specific instances
Track usage manually by time windowNo real cost separation, just estimation
RAW_BUFFERClick to expand / collapse

Problem

Conductor authenticates via OAuth to a single Anthropic account. All workspaces share that one account's subscription and billing. There is no way to associate different workspaces with different accounts.

This is a problem for users who work across multiple organizations or contexts (e.g., personal projects vs. client/business work) and need cost separation between them. Freelancers, consultants, and anyone with both personal and business Anthropic accounts hit this limitation.

Current workarounds (all inadequate)

WorkaroundWhy it doesn't work
Set ANTHROPIC_API_KEY per workspace in project settingsBills at pay-per-use API rates, not against the Max subscription — significantly more expensive
claude logout / claude login hook on workspace switchBreaks all other running workspaces that share the session
Run two Conductor app instancesUnsupported, fragile, no way to direct workspaces to specific instances
Track usage manually by time windowNo real cost separation, just estimation

Proposed solution

Allow users to bind a workspace (or group of workspaces) to a specific Anthropic account/subscription. This could look like:

  • Per-workspace account setting in workspace configuration (e.g., account: "personal" vs account: "business")
  • Account profiles that users can define once and assign to workspaces
  • OAuth sessions per workspace rather than a single global session

The key requirement is that usage in workspace A bills against Account A's Max subscription, and usage in workspace B bills against Account B's Max subscription — without requiring API keys at pay-per-use rates.

Use case

A developer has:

  • A personal Max account for side projects
  • A business Max account (via their company) for work projects

Both accounts have Max subscriptions. They want to run Conductor with workspaces for both contexts simultaneously, with each workspace's usage counting against the correct subscription.

Environment

  • Conductor on macOS
  • Multiple Anthropic accounts (each with Max subscriptions)

extent analysis

TL;DR

Implementing per-workspace Anthropic account binding is likely the most effective fix to achieve cost separation between different workspaces.

Guidance

  • Introduce a per-workspace account setting to allow users to bind a specific Anthropic account to each workspace, ensuring usage is billed against the correct subscription.
  • Consider implementing account profiles that users can define and assign to workspaces, simplifying the management of multiple Anthropic accounts.
  • Explore the possibility of using OAuth sessions per workspace instead of a single global session, which could help achieve the desired cost separation without requiring API keys at pay-per-use rates.
  • To verify the effectiveness of the solution, test the billing for each workspace to ensure it is correctly associated with the intended Anthropic account subscription.

Example

# Example workspace configuration with per-workspace account setting
workspaces:
  - name: personal-project
    account: personal
  - name: business-project
    account: business

Notes

The proposed solution requires modifications to the Conductor application to support per-workspace account binding, which may involve significant changes to the existing authentication and billing logic.

Recommendation

Apply a workaround by implementing per-workspace account binding, as it directly addresses the need for cost separation between workspaces and aligns with the proposed solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING