Moxie

Product Introduction

1. Definition: Moxie is a native macOS menu bar application (a local proxy server) that functions as a universal AI model router for Claude Code. It acts as a middleware layer, intercepting and redirecting API requests from the Claude Code CLI and VS Code extension to a user's configured portfolio of AI accounts and models.
2. Core Value Proposition: Moxie exists to decouple the user from a single AI provider within the Claude Code ecosystem. Its primary value is enabling uninterrupted AI-assisted coding workflows by allowing mid-task account switching when usage limits are hit, and providing centralized management for multiple AI models (including Claude, OpenAI ChatGPT, Google Gemini, DeepSeek, and local Ollama instances) from a single, familiar interface.

Main Features

1. Universal AI Model Router: Moxie operates as a local proxy on localhost:8060. It automatically configures Claude Code's settings (~/.claude/settings.json) to point its ANTHROPIC_BASE_URL to this local endpoint. Once configured, Moxie intelligently routes Claude Code's requests to the user's active account, whether it's an Anthropic Claude plan, an OpenAI API key, a Gemini session, or a local Ollama model. This technical integration supports both the CLI and VS Code extension.
2. Dynamic Account Switching with Session Persistence: This is a core technical innovation. When an active account hits its provider-enforced usage limit (e.g., Claude's 5-hour window), the user can select a different account from the Moxie menu bar. In-flight requests complete on the original account, and all subsequent requests are seamlessly routed to the new account. This allows a coding session in Claude Code to continue without restarting or manually reconfiguring the environment.
3. Real-Time Usage Limit Dashboard & Notifications: Moxie provides a live visual dashboard for each connected account, displaying the remaining capacity in both the 5-hour and weekly usage windows. This data is derived from actual API traffic. The app triggers native macOS notifications at 90% usage, upon limit exhaustion, and upon reset. A unique Dock icon gauge visually drains to reflect the active account's 5-hour limit consumption.
4. Secure Local-First Architecture: All credentials (OAuth tokens, API keys) are stored exclusively in the macOS Keychain, not on Moxie's servers. API requests are made directly from the user's Mac to the provider (Anthropic, OpenAI, etc.). Moxie's communication is limited to license validation, update checks, and pricing data, ensuring privacy and reducing latency.
5. Comprehensive Account Management & Playground: The app allows users to import existing Claude Code/Codex logins and add new accounts via OAuth or API key. A built-in Playground chat interface lets users test any account/model combination before relying on it in Claude Code. The system also supports full backup and restore of accounts, settings, and complete usage history.

Problems Solved

1. Pain Point: Workflow disruption due to AI provider usage limits. Developers using Claude Code for extended sessions are frequently blocked when they hit Claude's 5-hour or weekly message limits, forcing them to stop work or manage multiple, separate configurations.
2. Target Audience: Professional software developers and engineers who rely heavily on AI coding assistants like Claude Code for daily productivity. This includes full-stack developers, DevOps engineers, and technical leads who use AI for code generation, refactoring, debugging, and documentation, and who often exhaust standard plan limits.
3. Use Cases: Essential for marathon coding sessions, hackathons, or heavy refactoring projects where a single AI account's limits are insufficient. It is also critical for teams or individuals comparing outputs from different models (e.g., Claude 3.5 Sonnet vs. GPT-4o vs. local Llama 3) on the same codebase without changing tools. Finally, it serves as a cost-control tool for those mixing premium plans with more economical API calls or local models.

Unique Advantages

1. Differentiation: Unlike manually editing config files or running separate instances, Moxie provides a persistent, system-level management layer. Compared to other AI aggregators, it is hyper-specialized for the Claude Code workflow, offering deep, automatic integration that competitors lack. Its focus on mid-session switching is a unique solution to a specific, high-friction point.
2. Key Innovation: The stateful proxy model with session-aware routing is the key technical innovation. Moxie isn't just a switcher; it maintains context of active requests and manages the handoff between different backend providers transparently to Claude Code, which believes it is still communicating with a single Anthropic endpoint. This creates the illusion of a single, limitless AI assistant.

Frequently Asked Questions (FAQ)

1. Is Moxie safe to use with my API keys? Yes. Moxie employs a local-first, secure architecture. All API keys and OAuth tokens are stored exclusively in your macOS Keychain, the system's encrypted credential vault. API calls are made directly from your computer to the provider (OpenAI, Anthropic, etc.), meaning your sensitive keys never pass through or are stored on Moxie's servers.
2. Does using Moxie violate the terms of service for Claude or ChatGPT? No. Moxie operates as a legitimate client manager and local proxy. You are using your own paid subscriptions and API keys according to their respective terms. Moxie simply facilitates switching between accounts you legally own and manages the routing of requests, which is typically permitted under provider agreements.
3. Can I use Moxie with local LLMs like those in Ollama? Absolutely. Moxie has built-in support for Ollama and other OpenAI-compatible local endpoints. You can configure a local model (e.g., Llama 3, CodeLlama) as an "account" within Moxie and route Claude Code requests to it seamlessly, allowing you to mix and match cloud and local AI models within the same coding session.
4. What happens if Moxie is turned off or crashes? If the Moxie background service stops, Claude Code will lose its connection to the proxy (localhost:8060). Your Claude Code will revert to its default behavior, which typically means it will either fail to connect or use its own default configured account. Your credentials remain safe in the Keychain. Restarting Moxie will re-establish the connection and routing.
5. How does the licensing model work? Moxie offers a free 3-day trial. After that, it operates on a one-time purchase model: a Standard license ($39 for 2 years of updates) or a Lifetime license ($79). There is no subscription. The license is validated locally on your Mac, and the app self-updates from within the application.