claude-desktop-multiple-windows-different-api
Enables simultaneous access to official Claude subscriptions and custom third-party APIs within a single desktop environment.
Multiple windows for Claude Desktop with different APIs at the same time: keep your official Claude subscription in one window and run other windows on custom / third-party APIs (cc-switch). Windows. 多开 Claude Desktop,多个窗口同时使用不同 API(官方订阅 + 第三方 API 同时工作)。
- Run your official Claude subscription and third-party APIs in separate windows
- Switch between different API keys without closing the application
- Use multiple Claude instances simultaneously for different coding projects
Enables simultaneous access to official Claude subscriptions and custom third-party APIs within a single desktop environment. This optimizes cost management and provides access to specialized models without switching accounts or contexts.
Developers and power users requiring concurrent access to multiple LLM endpoints and subscription tiers within one interface.
https://github.com/TonF1917/claude-desktop-multiple-windows-...
By TonF1917
How to Get It
claude plugins install TonF1917/claude-desktop-multiple-windows-different-api
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me run my official Claude subscription and third-party APIs in separate windows
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 931 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 931 GitHub stars; contributors unknown; last commit 0d ago; license MIT.