PHI
PHI app icon

A local-first workspace for AI coding

Your AI coding tools,
in one window.

Set up models for Claude Code, Codex and Gemini CLI, then open a terminal right in PHI. Switch providers, manage tools and check usage without juggling windows.

Download PHI View on GitHub

macOS · Windows · Linux/Open source · MIT license

The built-in terminal currently requires macOS 13+. Install your CLIs separately.

Workspace illustration. CLI appearance depends on the version you install.

Why PHI exists

Setting things up
shouldn't be this much work.

Maybe you use Claude Code, Codex and Gemini CLI side by side. Each has its own settings. A new provider means editing three or four places; a new model means remembering which file you changed last time.

PHI brings those settings together. Add a provider once and use it across tools; run commands without leaving the app. No PHI account is needed. Configuration and statistics stay local, while model services use your own account or API key.

An independent fork of CC Switch, built with Tauri 2, Rust and React.

01Built-in terminal

Run your CLIs right in PHI.

Click “+” at the top right of an app page, or press ⌘T, then choose a directory. PHI checks for an installed CLI and launches it there. This works with nine tools, including Claude Code, Codex and Gemini CLI. Currently available on macOS 13+ only. If a CLI is missing, PHI shows installation guidance.

  • Settings and terminals, in tabs

    Switch between them in the same app. Change a provider, then run a command without opening another window.

  • Put sessions side by side

    Open two sessions of the same tool side by side: edit in one, check results in the other. Vertical splits work too.

  • Keep your preferred colors

    Follow PHI's light or dark theme, or pick a built-in palette. Your choice stays with you across app pages.

  • Leave the tab. Keep it running.

    Check usage or change settings on another page without interrupting the process. Come back and carry on typing.

  • A shell after your CLI exits

    Return to the same shell, with your working directory and previous output still there.

Interface illustration. The terminal uses native Ghostty rendering and currently requires macOS 13 or later.

02Local gateway

One model. More than one tool.

PHI runs a gateway on your computer. Claude Code and Codex use different protocols; the gateway handles supported conversions between them. Connect a provider and model without setting up each tool separately.

Routing
Send traffic to a chosen provider based on the app and the requested model.
Provider groups
Group several providers so there is another route to try when the primary one fails.
Failover
Try configured backup routes for eligible errors, and temporarily avoid routes that keep failing.
Direct connection
Prefer to skip the gateway? Keep the tool's original connection method.

Configuration is stored locally. When you use a model, request content and required credentials are sent to your chosen provider. PHI does not provide model services.

03Settings

Set it up once. Use it across tools.

Manage providers, MCP, Skills and prompts together, then apply them in the way each tool supports.

Providers and keys
Keep providers and models together and switch with a click. Subscription sign-in credentials are stored in the system keychain.
MCP and Skills
One list of servers and skills shows which tools they are installed in and whether they are enabled.
Prompts
Save your regular prompts in a library. Copy them when needed or write them into project configuration.
Project snapshots
Save providers, MCP, Skills and memory files as a project, then switch between work and personal setups with a click.
Accounts and sign-in
See which accounts need signing in again and manage default accounts in one place.

04Usage

Know where this month's budget went.

Sessions, tokens, costs, cache hits and active time are recorded locally. Follow daily trends or use a day-by-hour heatmap to see when you tend to use your tools most.

  • Break it down by app, provider or model

    See which tools and models account for your spending, beyond a single total.

  • Inspect individual requests

    Check the model, duration, tokens and cost of each request when a number needs explaining.

  • Keep an eye on long sessions

    Context usage charts and automatic compaction thresholds help you decide when to start a fresh session.

05Local data

Know where your data lives.

PHI has no project-operated cloud backend. Configuration, session statistics and usage records are stored locally in ~/.phi/. Subscription OAuth tokens use the system keychain. Viewing local settings and existing statistics does not require a PHI cloud service. Online model requests go from the CLI or local gateway to your chosen provider.

Works with the tools you already use.

Let PHI manage configuration for Claude Code, Claude Desktop, Codex, Gemini CLI and Grok Build. OpenCode, OpenClaw, Hermes, Pi and MiniMax Code connect in coexistence mode, leaving their original configuration files untouched.

  • Claude Code
  • Claude Desktop
  • Codex
  • Gemini CLI
  • Grok Build
  • OpenCode
  • OpenClaw
  • Hermes Agent
  • Pi
  • MiniMax Code

06Getting started

Start with a tool you know.

You don't need to configure everything at once. Connect one tool, then build out your workspace at your own pace.

  1. Install PHI and your CLI

    PHI manages and launches tools. Install each CLI using its official instructions, or keep using an existing installation.

  2. Add a provider and choose a connection

    Enter your model service details. On the Routing page, choose a direct provider connection or a gateway route group.

  3. Open a project and get to work

    On macOS 13+, click “+” on an app page and choose a directory to launch a CLI. On other platforms, use your external terminal.

Common questions

A few things before you download.

Does PHI include models or free credits?

PHI is an open-source desktop tool and does not include model credits. Bring your own provider API key or a subscription account supported by your tool. Your chosen service provider charges for model usage.

Can I run CLIs inside PHI on Windows or Linux?

The built-in terminal currently requires macOS 13 or later. On Windows and Linux, use PHI to manage settings, connect models and track usage, and run your CLIs in an external terminal.

Where do my keys and requests go?

Main configuration and usage data stay on your computer; subscription OAuth tokens go in the system keychain. Model requests and required credentials are sent to the provider you configure. Connect only to services you trust and protect your local data.

Does every tool support every model and feature?

Support depends on the tool, model and provider. The gateway can convert supported protocols, but capabilities such as tool calling and context length still vary. Try a small task after connecting to check that the setup works for you.

How do I update or report a problem?

Choose “Check for updates” in the app, or visit GitHub Releases for the latest version. Report problems on GitHub Issues with your OS version, tool name and steps to reproduce. Remember to remove any keys.

Settings sorted. Back to work.

Bring your tools together.

Choose a package for your operating system. Check GitHub Releases for available versions, architectures and files.

macOS Apple Silicon / IntelBuilt-in terminal: macOS 13+ Windows x64 / ARM64Windows 10 / 11 Linux x64 / ARM64AppImage / deb / rpm

All links above open the release page; downloads do not start automatically. You can alsobuild from source