What inspired you to build this? Switching between Claude backends — local proxies, OpenRouter, Vertex AI, Bedrock — means exporting different env vars every time. One wrong variable and the session breaks silently. What problem were you trying to solve? Claude Code has no native profile system. Developers who run it against multiple environments manage everything outside the tool — shell exports, wrapper scripts, .env files. cc-wrapper adds a named-profile layer so switching contexts takes one command instead of manual env management. How did the approach evolve? Started as a shell alias concept but cross-platform support killed that quickly. Moved to a proper Node.js CLI so config paths, env injection, and process spawning work natively on Windows, macOS, and Linux. The interactive env var selector came from realizing the official Claude docs list 25+ variables — users shouldn't need to memorize them. The tool surfaces them with descriptions and example values inline.

Claude Code Wrapper

Cross-platform wrapper for Claude Code with named profiles.

Cross-platform wrapper for Claude Code with named profiles.