Feature Request: Decouple Claude Code CLI Tool from Claude Models

Background

The developer community currently has access to numerous open-source CLI build tools including Opencode, Gemini CLI, Charm Crush, Cline, and others. Additionally, various LLM models offer better performance for specific tasks in terms of pricing, simplicity, or specialized capabilities.

Problem Statement

1. Geographic restrictions: Developers in certain regions (e.g., China) cannot access Claude models due to regulatory restrictions
2. Model limitations: Some projects require different models due to budget constraints or specific task requirements
3. Bundled pricing: Current bundling of the tool with the model limits flexibility for users

Proposed Solution

Separate Claude Code into two distinct components:

1. Build tool: The CLI interface and tooling capabilities
2. Model provider: LLM model access and usage

Benefits for Users

• Choose the most cost-effective or task-appropriate model for their specific needs
• Access to the build tool regardless of model availability restrictions
• More flexible pricing structure based on actual usage patterns

Benefits for Anthropic

1. Expanded market reach: Monetize the build tool in regions where Claude models aren't accessible
2. Usage-based pricing: Address model abuse concerns by implementing pay-per-use billing
3. Competitive advantage: Establish Claude Code as the industry-standard build tool
4. Market leadership: Potentially eliminate competition by offering superior tooling flexibility

Use Cases

• Developers in restricted regions using the build tool with accessible models
• Budget-conscious projects requiring cost-effective model alternatives
• Specialized tasks requiring models with specific domain expertise

Would appreciate consideration of this feature request to increase accessibility and flexibility for the developer community.