claude-switch 1.0.0__tar.gz

claude_switch-1.0.0/.claude/commands/spec.md

@@ -0,0 +1,134 @@
+# Requirements Gathering Generation
+
+Workflow Stage: Requirements Gathering
+
+First, generate an initial set of requirements in EARS format based on the feature idea, then iterate with the user to refine them until they are complete and accurate.
+
+Don't focus on code exploration in this phase. Instead, just focus on writing requirements which will later be turned into
+a design.
+
+**Constraints:**
+
+- The model MUST create a 'specs/{feature_name}/requirements.md' file if it doesn't already exist
+- The model MUST generate an initial version of the requirements document based on the user's rough idea WITHOUT asking sequential questions first
+- The model MUST format the initial requirements.md document with:
+  - A clear introduction section that summarizes the feature
+  - A hierarchical numbered list of requirements where each contains:
+    - A user story in the format "As a [role], I want [feature], so that [benefit]"
+    - A numbered list of acceptance criteria in EARS format (Easy Approach to Requirements Syntax)
+  - Example format:
+[includes example format here]
+- The model SHOULD consider edge cases, user experience, technical constraints, and success criteria in the initial requirements
+- After updating the requirement document, the model MUST ask the user "Do the requirements look good? If so, we can move on to the design." using the 'userInput' tool.
+- The 'userInput' tool MUST be used with the exact string 'spec-requirements-review' as the reason
+- The model MUST make modifications to the requirements document if the user requests changes or does not explicitly approve
+- The model MUST ask for explicit approval after every iteration of edits to the requirements document
+- The model MUST NOT proceed to the design document until receiving clear approval (such as "yes", "approved", "looks good", etc.)
+- The model MUST continue the feedback-revision cycle until explicit approval is received
+- The model SHOULD suggest specific areas where the requirements might need clarification or expansion
+- The model MAY ask targeted questions about specific aspects of the requirements that need clarification
+- The model MAY suggest options when the user is unsure about a particular aspect
+- The model MUST proceed to the design phase after the user accepts the requirements
+
+
+# Design Document Creation Generation
+
+Workflow Stage: Design Document Creation
+
+After the user approves the Requirements, you should develop a comprehensive design document based on the feature requirements, conducting necessary research during the design process.
+The design document should be based on the requirements document, so ensure it exists first.
+
+**Constraints:**
+
+- The model MUST create a 'specs/{feature_name}/design.md' file if it doesn't already exist
+- The model MUST identify areas where research is needed based on the feature requirements
+- The model MUST conduct research and build up context in the conversation thread
+- The model SHOULD NOT create separate research files, but instead use the research as context for the design and implementation plan
+- The model MUST summarize key findings that will inform the feature design
+- The model SHOULD cite sources and include relevant links in the conversation
+- The model MUST create a detailed design document at 'specs/{feature_name}/design.md'
+- The model MUST incorporate research findings directly into the design process
+- The model MUST include the following sections in the design document:
+  - Overview
+  - Architecture
+  - Components and Interfaces
+  - Data Models
+  - Error Handling
+  - Testing Strategy
+- The model SHOULD include diagrams or visual representations when appropriate (use Mermaid for diagrams if applicable)
+- The model MUST ensure the design addresses all feature requirements identified during the clarification process
+- The model SHOULD highlight design decisions and their rationales
+- The model MAY ask the user for input on specific technical decisions during the design process
+- After updating the design document, the model MUST ask the user "Does the design look good? If so, we can move on to the implementation plan." using the 'userInput' tool.
+- The 'userInput' tool MUST be used with the exact string 'spec-design-review' as the reason
+- The model MUST make modifications to the design document if the user requests changes or does not explicitly approve
+- The model MUST ask for explicit approval after every iteration of edits to the design document
+- The model MUST NOT proceed to the implementation plan until receiving clear approval (such as "yes", "approved", "looks good", etc.)
+- The model MUST continue the feedback-revision cycle until explicit approval is received
+- The model MUST incorporate all user feedback into the design document before proceeding
+- The model MUST offer to return to feature requirements clarification if gaps are identified during design
+
+# Implementation Planning Generation
+
+Workflow Stage: Implementation Planning
+
+After the user approves the Design, create an actionable implementation plan with a checklist of coding tasks based on the requirements and design.
+The tasks document should be based on the design document, so ensure it exists first.
+
+**Constraints:**
+
+- The model MUST create a 'specs/{feature_name}/tasks.md' file if it doesn't already exist
+- The model MUST return to the design step if the user indicates any changes are needed to the design
+- The model MUST return to the requirement step if the user indicates that we need additional requirements
+- The model MUST create an implementation plan at 'specs/{feature_name}/tasks.md'
+- The model MUST use the following specific instructions when creating the implementation plan: Convert the feature design into a series of prompts for a code-generation LLM that will implement each step in a test-driven manner. Prioritize best practices, incremental progress, and early testing, ensuring no big jumps in complexity at any stage. Make sure that each prompt builds on the previous prompts, and ends with wiring things together. There should be no hanging or orphaned code that isn't integrated into a previous step. Focus ONLY on tasks that involve writing, modifying, or testing code.
+- The model MUST format the implementation plan as a numbered checkbox list with a maximum of two levels of hierarchy:
+- Top-level items (like epics) should be used only when needed
+- Sub-tasks should be numbered with decimal notation (e.g., 1.1, 1.2, 2.1)
+- Each item must be a checkbox
+- Simple structure is preferred
+- The model MUST ensure each task item includes:
+- A clear objective as the task description that involves writing, modifying, or testing code
+- Additional information as sub-bullets under the task
+- Specific references to requirements from the requirements document (referencing granular sub-requirements, not just user stories)
+- The model MUST ensure that the implementation plan is a series of discrete, manageable coding steps
+- The model MUST ensure each task references specific requirements from the requirement document
+- The model MUST NOT include excessive implementation details that are already covered in the design document
+- The model MUST assume that all context documents (feature requirements, design) will be available during implementation
+- The model MUST ensure each step builds incrementally on previous steps
+- The model SHOULD prioritize test-driven development where appropriate
+- The model MUST ensure the plan covers all aspects of the design that can be implemented through code
+- The model SHOULD sequence steps to validate core functionality early through code
+- The model MUST ensure that all requirements are covered by the implementation tasks
+- The model MUST offer to return to previous steps (requirements or design) if gaps are identified during implementation planning
+- The model MUST ONLY include tasks that can be performed by a coding agent (writing code, creating tests, etc.)
+- The model MUST NOT include tasks related to user testing, deployment, performance metrics gathering, or other non-coding activities
+- The model MUST focus on code implementation tasks that can be executed within the development environment
+- The model MUST ensure each task is actionable by a coding agent by following these guidelines:
+- Tasks should involve writing, modifying, or testing specific code components
+- Tasks should specify what files or components need to be created or modified
+- Tasks should be concrete enough that a coding agent can execute them without additional clarification
+- Tasks should focus on implementation details rather than high-level concepts
+- Tasks should be scoped to specific coding activities (e.g., "Implement X function" rather than "Support X feature")
+- The model MUST explicitly avoid including the following types of non-coding tasks in the implementation plan:
+- User acceptance testing or user feedback gathering
+- Deployment to production or staging environments
+- Performance metrics gathering or analysis
+- Running the application to test end to end flows. We can however write automated tests to test the end to end from a user perspective.
+- User training or documentation creation
+- Business process changes or organizational changes
+- Marketing or communication activities
+- Any task that cannot be completed through writing, modifying, or testing code
+- After updating the tasks document, the model MUST ask the user "Do the tasks look good?" using the 'userInput' tool.
+- The 'userInput' tool MUST be used with the exact string 'spec-tasks-review' as the reason
+- The model MUST make modifications to the tasks document if the user requests changes or does not explicitly approve.
+- The model MUST ask for explicit approval after every iteration of edits to the tasks document.
+- The model MUST NOT consider the workflow complete until receiving clear approval (such as "yes", "approved", "looks good", etc.).
+- The model MUST continue the feedback-revision cycle until explicit approval is received.
+- The model MUST stop once the task document has been approved.
+
+**This workflow is ONLY for creating design and planning artifacts. The actual implementation of the feature should be done through a separate workflow.**
+
+- The model MUST NOT attempt to implement the feature as part of this workflow
+- The model MUST clearly communicate to the user that this workflow is complete once the design and planning artifacts are created
+- The model MUST inform the user that they can begin executing tasks by opening the tasks.md file, and clicking "Start task" next to task items.

claude_switch-1.0.0/.claude/settings.local.json

@@ -0,0 +1,50 @@
+{
+  "permissions": {
+    "allow": [
+      "mcp__filesystem__create_directory",
+      "Bash(rm:*)",
+      "Bash(touch:*)",
+      "Bash(grep:*)",
+      "Bash(ls:*)",
+      "Bash(source:*)",
+      "Bash(find:*)",
+      "Bash(mv:*)",
+      "Bash(mkdir:*)",
+      "Bash(tree:*)",
+      "Bash(ruff:*)",
+      "Bash(touch:*)",
+      "Bash(cat:*)",
+      "Bash(ruff check:*)",
+      "Bash(pytest:*)",
+      "Bash(python:*)",
+      "Bash(python -m pytest:*)",
+      "Bash(python3 -m pytest:*)",
+      "WebFetch(domain:docs.anthropic.com)",
+      "Bash(uv pip install:*)",
+      "Bash(python:*)",
+      "Bash(uv run:*)",
+      "Bash(ls:*)",
+      "Bash(source:*)",
+      "Bash(echo:*)",
+      "mcp__sequential-thinking__sequentialthinking",
+      "Bash(pyenv:*)",
+      "Bash(~/.pyenv/versions/3.11.13/bin/python:*)",
+      "Bash(~/Library/Python/3.9/bin/cs list)",
+      "Bash(cs list:*)",
+      "Bash(~/.pyenv/versions/3.11.13/bin/cs list:*)",
+      "Bash(~/.pyenv/versions/3.11.13/bin/cs:*)",
+      "mcp__ide__executeCode",
+      "mcp__filesystem__list_directory",
+      "mcp__filesystem__read_file",
+      "mcp__filesystem__directory_tree",
+      "mcp__filesystem__write_file",
+      "mcp__context7__resolve-library-id",
+      "mcp__context7__get-library-docs",
+      "mcp__search__brave_web_search",
+      "mcp__perplexity-ask__perplexity_ask",
+      "Bash(pip install:*)",
+      "Bash(cs:*)"
+    ],
+    "deny": []
+  }
+}

claude_switch-1.0.0/.gitignore

@@ -0,0 +1,11 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+.DS_Store
+
+# Virtual environments
+.venv

claude_switch-1.0.0/.python-version

@@ -0,0 +1 @@
+3.11

claude_switch-1.0.0/CLAUDE.md

@@ -0,0 +1,140 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+Claude Switch is a Python CLI tool for managing multiple Anthropic Claude API configurations. It allows users to easily switch between different environments (development, testing, production) with support for both auth_token and api_key authentication methods.
+
+## Core Architecture
+
+### Main Components
+
+- **CLI Interface** (`claude_switch/cli.py`): Click-based command line interface with interactive features using questionary
+- **Configuration Manager** (`claude_switch/config.py`): Handles JSON config file management, credential storage, and shell integration
+- **Core Logic** (`claude_switch/core.py`): Business logic for configuration operations and environment management
+
+### Key Features
+
+- Multi-configuration management with secure credential storage
+- Interactive configuration selection with arrow key navigation
+- Shell integration for automatic environment variable loading
+- Support for both API keys and auth tokens with custom naming
+- Cross-shell compatibility (bash, zsh, fish)
+
+## Development Commands  
+
+### Installation and Setup
+
+```bash
+# Install in development mode using uv (recommended)
+uv pip install -e .
+
+# Or using pip
+pip install -e .
+
+# Activate virtual environment if using .venv
+source .venv/bin/activate
+```
+
+### Testing Commands
+
+```bash
+# Run the CLI tool directly
+python -m claude_switch.cli
+
+# Test installed commands
+cs --help
+claude-switch --help
+
+# Verify installation
+cs --version
+```
+
+### Package Management
+
+```bash
+# Build package for distribution
+python -m build
+
+# Install from local build
+pip install dist/claude_switch-1.0.0-py3-none-any.whl
+```
+
+## Configuration Structure
+
+The tool uses `~/.claude-switch/config.json` for configuration storage with this structure:
+
+```json
+{
+  "version": "2.0",
+  "active": "config_name",
+  "configs": {
+    "config_name": {
+      "base_url": "https://api.anthropic.com",
+      "api_keys": ["key1", "key2|custom_name"],
+      "auth_tokens": ["token1", "token2|custom_name"], 
+      "note": "Description",
+      "active_key": 0,
+      "active_auth": -1
+    }
+  }
+}
+```
+
+## Key Implementation Details
+
+### Interactive Features
+
+- Uses `questionary` for arrow key navigation in configuration selection
+- Supports ESC key cancellation with confirmation prompts
+- Visual indicators (✅) for active configurations and credentials
+
+### Shell Integration
+
+- Generates dynamic shell wrapper scripts in `~/.claude-switch/`
+- Creates `cs-wrapper.sh` for command aliases and environment loading
+- Automatic environment variable export via `env.sh`
+
+### Credential Management
+
+- Supports credential naming with pipe separator (`credential|name`)
+- Automatic credential masking for display (`key[:4]...key[-4:]`)
+- Per-configuration active credential tracking
+
+### Error Handling
+
+- Graceful handling of missing configurations
+- JSON repair for corrupted config files
+- File permission management (0o600 for config files)
+
+## Development Notes
+
+### Dependencies
+
+- `click>=8.0.0`: CLI framework
+- `questionary>=2.0.0`: Interactive prompts with arrow key support
+- `json-repair>=0.30.0`: Robust JSON parsing and repair
+
+### Code Style
+
+- Use existing patterns for configuration management
+- Follow Click conventions for command definitions
+- Maintain backward compatibility for config file format
+- Use type hints where appropriate
+
+### Shell Integration Testing
+
+When testing shell integration:
+
+```bash
+# Test shell wrapper generation
+cs init
+
+# Verify generated files
+ls -la ~/.claude-switch/
+
+# Test environment loading
+source ~/.claude-switch/cs-wrapper.sh
+cs current --export
+```

claude_switch-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Claude Switch
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

claude_switch-1.0.0/PKG-INFO

@@ -0,0 +1,290 @@
+Metadata-Version: 2.4
+Name: claude-switch
+Version: 1.0.0
+Summary: Anthropic Claude API 配置管理工具，支持多环境切换
+Project-URL: Homepage, https://github.com/your-username/claude-switch
+Project-URL: Repository, https://github.com/your-username/claude-switch
+Project-URL: Documentation, https://github.com/your-username/claude-switch#readme
+Project-URL: Issues, https://github.com/your-username/claude-switch/issues
+Project-URL: Changelog, https://github.com/your-username/claude-switch/releases
+Author-email: Claude <noreply@anthropic.com>
+License: MIT
+License-File: LICENSE
+Keywords: anthropic,api,claude,cli,config,environment,switch
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Systems Administration
+Classifier: Topic :: Utilities
+Requires-Python: >=3.8
+Requires-Dist: click>=8.0.0
+Requires-Dist: json-repair>=0.30.0
+Requires-Dist: questionary>=2.0.0
+Description-Content-Type: text/markdown
+
+# Claude Switch
+
+A Python CLI tool for managing multiple Anthropic Claude API configurations with seamless environment switching.
+
+## Features
+
+- **Multi-configuration management**: Handle multiple Anthropic API configurations
+- **One-click switching**: Switch between development, testing, and production environments
+- **Dual authentication**: Support for both `auth_token` and `api_key` authentication methods
+- **Automatic environment activation**: Environment variables automatically生效 after configuration switch
+- **Secure storage**: Configuration file permission protection with encrypted credential storage
+- **Interactive navigation**: Arrow key navigation with color highlighting
+- **Backup mechanism**: Automatic configuration file backup to prevent data loss
+
+## Installation
+
+### pip Installation (Recommended)
+```bash
+pip install claude-switch
+
+# Or using pipx (recommended to avoid dependency conflicts)
+pipx install claude-switch
+```
+
+### From Source
+```bash
+git clone https://github.com/your-username/claude-switch.git
+cd claude-switch
+
+# Using uv (recommended)
+uv pip install -e .
+
+# Or using pip
+pip install -e .
+```
+
+## Getting Started
+
+### Initialization
+After installation, initialize shell integration:
+```bash
+cs init
+```
+
+Initialization will:
+- Automatically detect your shell environment (bash/zsh/fish)
+- Generate dynamic shell configuration files
+- Add configuration to your shell profile
+- Optionally add the first configuration
+
+Restart your terminal or run:
+```bash
+source ~/.claude-switch/cs-wrapper.sh
+```
+
+### Verification
+```bash
+# Check version
+cs --version
+
+# View help
+cs --help
+
+# Add first configuration
+cs add
+```
+
+## Commands
+
+### Interactive Operations
+- `cs` - Interactive configuration selection (arrow key navigation)
+- `cs add` - Interactive new configuration addition
+
+### Management Commands
+- `cs list` - List all configurations
+- `cs use <name>` - Switch to specified configuration
+- `cs current` - Display current configuration
+- `cs edit <name>` - Edit configuration information
+- `cs remove <name>` - Remove configuration
+- `cs add-credential <config>` - Add credentials to specified configuration
+
+### Environment Export
+- `cs current --export` - Output executable export commands
+
+## Usage Examples
+
+### Adding a Configuration
+```bash
+# Interactive configuration addition
+cs add
+# Enter configuration name, Base URL, and description
+
+# Add credentials to configuration
+cs add-credential work
+```
+
+### Viewing and Managing Configurations
+```bash
+# View all configurations
+cs list
+# Output:
+# → work - 工作账号 [https://api.anthropic.com] (0tokens, 1keys) [key1]
+#   personal - 个人账号 [https://api.anthropic.com] (1tokens, 0keys) [token1]
+
+# Interactive selection
+cs
+# Use arrow keys to select, press Enter to confirm
+
+# Quick switch
+cs use work
+```
+
+### Configuration Management
+```bash
+# Edit configuration information
+cs edit work
+
+# View current configuration
+cs current
+# Output: 当前配置: work - 工作账号 [https://api.anthropic.com] (0tokens, 1keys) [key1]
+
+# Export environment variables
+cs current --export
+# Output: export ANTHROPIC_BASE_URL="..."; export ANTHROPIC_API_KEY="..."
+```
+
+## Configuration Structure
+
+Configuration is stored in `~/.claude-switch/config.json`:
+
+```json
+{
+  "version": "2.0",
+  "active": "work",
+  "configs": {
+    "work": {
+      "base_url": "https://api.anthropic.com",
+      "api_keys": ["sk-xxx"],
+      "auth_tokens": [],
+      "note": "工作账号",
+      "active_key": 0,
+      "active_auth": -1
+    },
+    "personal": {
+      "base_url": "https://api.anthropic.com",
+      "api_keys": [],
+      "auth_tokens": ["sk-yyy"],
+      "note": "个人账号",
+      "active_key": -1,
+      "active_auth": 0
+    }
+  }
+}
+```
+
+## Interactive Interface Features
+
+- **Cursor highlighting**: Current selection line highlighted in green
+- **Status indicators**: Green arrow (→) indicates active configuration
+- **Rich information**: Shows configuration name, description, URL, credential count and type
+- **Arrow navigation**: Supports up/down arrow key selection with Enter confirmation
+
+## Security Features
+
+- **File permissions**: Configuration file automatically set to 0o600 (user-readable only)
+- **Sensitive information masking**: Automatic credential masking during display
+- **Automatic backup**: Automatic backup creation when configuration file is corrupted
+- **Version compatibility**: Automatic configuration version upgrade handling
+
+## Advanced Usage
+
+### Manual Configuration Editing
+You can directly edit the configuration file `~/.claude-switch/config.json`. The system automatically handles format errors and creates backups.
+
+### Environment Variable Settings
+```bash
+# Automatic activation (requires initialization)
+cs use production
+
+# Manual activation
+eval $(cs current --export)
+```
+
+### Shell Integration
+After initialization, the following aliases are automatically available:
+- `cs` - Main command
+- `csu` - Quick configuration switching
+- `csc` - View current configuration
+- `css` - Manual environment variable reload
+
+## Troubleshooting
+
+### Installation Issues
+
+**Problem: cs command not found**
+```bash
+# Check if installed correctly
+pip list | grep claude-switch
+
+# Check PATH settings
+echo $PATH
+
+# Reinstall
+pip install --force-reinstall claude-switch
+```
+
+**Problem: Permission errors**
+```bash
+# Use user installation
+pip install --user claude-switch
+
+# Or use pipx
+pipx install claude-switch
+```
+
+### Initialization Issues
+
+**Problem: Shell integration not working**
+```bash
+# Manually source configuration file
+source ~/.claude-switch/cs-wrapper.sh
+
+# Check if configuration files exist
+ls -la ~/.claude-switch/
+
+# Reinitialize
+cs init
+```
+
+**Problem: Environment variables not taking effect**
+```bash
+# Manually load environment variables
+source ~/.claude-switch/env.sh
+
+# Or use export command
+eval $(cs current --export)
+```
+
+## Compatibility
+
+- **Supported Python versions**: 3.8+
+- **Supported operating systems**: macOS, Linux, Windows
+- **Supported shells**: bash, zsh, fish
+- **Supported installation methods**: pip, pipx, conda, uv
+
+## Getting Help
+
+If you encounter issues:
+1. View `cs --help` for command assistance
+2. Check configuration files in `~/.claude-switch/` directory
+3. Submit an Issue on GitHub: https://github.com/your-username/claude-switch/issues
+
+## License
+
+MIT License