[Feature]: Add multiple Claude accounts, allowing Claude binary path to be configured per project or per chat

[alvax64]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

I use two different Claude Code Max accounts: one for work and one for personal projects.

Today, the Claude binary path appears to be configured globally, which makes it hard to work across multiple projects in parallel. If I switch from a work project to a personal one, I need to manually change the global binary path before sending a message. That adds friction and makes parallel workflows error-prone.

One of the strengths of T3 Code is that it makes parallel work across projects feel smooth, but this part becomes a bottleneck for users who need different Claude binaries or account contexts depending on the project.

Proposed solution

Allow the Claude binary path to be configured at a more local scope instead of only globally.

A few possible ways this could work:

• per project: each project can override the default Claude binary path
• per chat: a chat/session can choose which Claude binary to use
• fallback model: global default remains, but project/chat settings can override it

From a UX perspective, it would help if the active binary were visible somewhere in the chat or project settings, and easy to change before sending a message.

Why this matters

This would help users who:

• separate work and personal Claude accounts
• use different binaries or wrappers for different environments
• regularly jump between multiple projects in parallel

The main benefit is reducing setup friction and avoiding mistakes caused by changing a global setting back and forth.

Smallest useful scope

The smallest version that would still solve this for me would be:

• keep the current global default
• add a per-project override for the Claude binary path
• use that override automatically for chats created inside that project

Even just per-project support would remove most of the manual switching.

Alternatives considered

Current workaround: manually change the global binary path every time I switch contexts.

That works, but it is inconvenient and easy to forget when moving between work and personal projects.

A broader alternative is full multi-account/profile switching as described in #229, but this request does not require that full feature set. A scoped binary-path override would already solve the practical problem for my workflow.

Risks or tradeoffs

A few things that may need to be defined clearly:

• precedence between global, project, and chat-level settings
• what happens if a configured binary path no longer exists
• whether changing the selected binary should affect already-running chats or only new messages/sessions
• avoiding confusion if the active binary is not clearly shown in the UI

Examples or references

Related issue: #229 support quick switching between multiple Codex accounts / auth profiles

This request is specifically about selecting the executable path per project or per chat, rather than only switching auth profiles globally.

Contribution

• I would be open to helping implement this.