# CC Paw
English | [δΈζ](README.zh.md)
**A desktop GUI for managing your [Claude Code](https://claude.ai/code) and Codex workflows.**
[](package.json)
[](LICENSE)
[](#platform-support)
[](https://electronjs.org/)
[](https://react.dev/)
[](https://www.typescriptlang.org/)
---
CC Paw is built for people who run Claude Code and Codex across many projects and want one clear, visual workspace instead of scattered terminals and config files. It gives each project a persistent session, real-time status, and timely notifications so you can focus on decisions instead of process.
It also turns Claude Code and Codex setup into a visual workflow: system prompts (`CLAUDE.md`), skills, MCP servers, plugins, project docs, and usage analytics are all managed from the UI. Whether you are non-technical or highly technical, CC Paw makes project management and vibecoding faster, clearer, and easier to sustain.
## Get the app
- **Installers (recommended):** download the latest **DMG** (macOS) or **Setup .exe** (Windows) from [GitHub Releases](https://github.com/HyacinH/cc-paw/releases).
- **macOS install tip (Gatekeeper):** if macOS shows "`CC Paw` is damaged and can't be opened", install to `Applications` first, then run:
```bash
sudo xattr -rd com.apple.quarantine "/Applications/CC Paw.app"
```
- **Run from source:** clone the repo, run `npm install`, then `npm run dev` (see [Quick Start](#quick-start) for details). You need **Claude Code** and/or **Codex** CLI installed with populated `~/.claude/` and/or `~/.codex/` directories to use all features.
- **Build an installer locally:** `npm run package` outputs platform-specific artifacts under `release/` (host OS only).
## Core features
### Project workspace (multi-project, sessions, docs, settings)
Core project-facing workflows are centralized in one workspace (screenshot below):
- **Multi-project sessions:** one persistent CLI terminal per project (Claude Code or Codex), so switching projects never drops context.
- **Session lifecycle:** start a new chat when needed and reopen archived conversations for follow-up work.
- **Project organization:** rename projects, switch quickly in the sidebar, and track state with per-project status indicators.
- **Project Docs (`docs/`):** edit Markdown with live preview and autosave, then keep project references in one place.
- **Project settings:** edit shared CLI settings (`~/.claude/settings.json`, `~/.codex/config.toml`) directly from the UI.
- **CLI runtime switching:** choose Claude Code or Codex in Settings to control active session runtime and config scope.
### CLI switching in Settings
Use the Settings page to choose the active CLI runtime (Claude Code or Codex). This controls which terminal environment and configuration scope are applied in project sessions.
### Plugin marketplace
Plugin workflows are grouped in one place (screenshot below):
- Discover/filter official marketplace plugins
- One-click install with live terminal output
- Install scope selection: **user** (`~/.claude`) or **project**
- Manage installed plugins (enable/disable/uninstall)
- Run `claude plugin` and `npx skills` commands from the app
### Token usage analytics
Usage and cost insights are shown in a dedicated dashboard (screenshot below):
- Reads Claude Code JSONL logs from `~/.claude/projects/` and Codex session logs from `~/.codex/sessions/`
- Aggregated totals (input/output/cache) with estimated cost
- Custom date-range filtering
- Bar charts by hour, day, week, or month
- Per-project breakdown with expandable details
### System prompts & settings
Maintain global and project-level instruction files in Monaco Editor (`CLAUDE.md` for Claude Code, `AGENTS.md` for Codex).
### Skills manager
Manage skill files in `~/.claude/skills/` and `~/.codex/skills/`, including URL import.
### MCP server configuration
Edit and validate MCP server entries for both runtimes (`~/.claude.json` and `~/.codex/config.toml`) before saving.
---
## Platform Support
| Platform | Status | Notes |
| ----------- | ----------------- | -------------------------------------------------------- |
| **macOS** | β
Fully supported | Native `hiddenInset` title bar, login-shell PATH capture |
| **Windows** | β
Supported | Native system title bar, ConPTY terminal, NSIS installer |
| Linux | π§ Untested | Likely works; PTY and file paths are cross-platform |
### Prerequisites
**All platforms:**
- **Node.js** 18+
- **npm** 9+
- **Claude Code** and/or **Codex** CLI installed (`~/.claude/` and/or `~/.codex/` should exist)
**Windows only** β `node-pty` is a native C++ module and requires a compiler toolchain. Run the following in an **Administrator** PowerShell:
```powershell
winget install Microsoft.VisualStudio.2022.BuildTools
winget install Python.Python.3.11
```
After installing Build Tools, open **Visual Studio Installer β Modify**:
- **Workloads** tab: check **Desktop development with C++**
- **Individual components** tab: search `Spectre` and check **MSVC v143 - VS 2022 C++ x64/x86 Spectre-mitigated libs**
> The Spectre-mitigated libs are **not selected by default** but are required by `node-gyp`. Without them, `npm install` will fail with a Spectre or `node-gyp` error.
Then run in **CMD or PowerShell** (not Git Bash β path handling differs):
```cmd
npm install
```
> **Minimum Windows version:** Windows 10 1903 (Build 18362) or later β required for ConPTY.
---
## Quick Start
```bash
# Clone the repository
git clone