desktop-cc-gui

Name: desktop-cc-gui
Author: zhukunpenglinyutong

Issues

Multi-engine AI coding desktop client (Tauri). Claude Code, Codex, Gemini, OpenCode, DeepSeek Harness and more in one GUI.

4,188stars

372forks

TypeScript

Installation

# Add to your Claude Code skills
git clone https://github.com/zhukunpenglinyutong/desktop-cc-gui

Getting Started

Guides for using cli tools skills like desktop-cc-gui.

Getting Started with AI Skills
First-time install walkthrough for Claude Code, Codex CLI, and ChatGPT.
SkillsLLM Features Guide
Voting, bookmarks, comments, comparison pages, and security scanning explained.
What is an AI Skills Marketplace?
Definitions, how marketplaces work, and how to choose between them in 2026.

Security ReportIssues

Last scanned: 8/17/2026

{
  "issues": [
    {
      "type": "npm-audit",
      "message": "@chevrotain/cst-dts-gen: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "@chevrotain/gast: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "@excalidraw/excalidraw: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "@excalidraw/mermaid-to-excalidraw: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "@hono/node-server: Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "@mermaid-js/parser: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "@xmldom/xmldom: xmldom: Uncontrolled recursion in XML serialization leads to DoS",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "ajv: ajv has ReDoS when using `$data` option",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "brace-expansion: brace-expansion: Zero-step sequence causes process hang and memory exhaustion",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "chevrotain: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "dompurify: DOMPurify contains a Cross-site Scripting vulnerability",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "fast-uri: fast-uri vulnerable to host confusion via literal backslash authority delimiter",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "flatted: flatted vulnerable to unbounded recursion DoS in parse() revive phase",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "hono: Hono: ReDoS in CORS middleware via Access-Control-Request-Headers",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "immutable: Immutable.js `List` 32-bit trie overflow → unrecoverable DoS",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "ip-address: ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "js-yaml: JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "langium: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "lodash-es: lodash vulnerable to Code Injection via `_.template` imports key names",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "mermaid: Vulnerability found",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "minimatch: minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "nanoid: Predictable results in nanoid generation when given non-integer values",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "pdfjs-dist: PDF.js: Arbitrary JavaScript execution upon opening a malicious PDF ",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "picomatch: Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "postcss: PostCSS has XSS via Unescaped </style> in its CSS Stringify Output",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "rollup: Rollup 4 has Arbitrary File Write via Path Traversal",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "undici: undici vulnerable to downstream response desynchronization via retry interceptor",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "uuid: uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "vite: Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "vitest: When Vitest UI server is listening, arbitrary file can be read and executed",
      "severity": "critical"
    },
    {
      "type": "npm-audit",
      "message": "ws: ws: Uninitialized memory disclosure",
      "severity": "high"
    },
    {
      "type": "npm-audit",
      "message": "xlsx: Prototype Pollution in sheetJS",
      "severity": "high"
    }
  ],
  "status": "FAILED",
  "scannedAt": "2026-08-17T04:40:47.280Z",
  "npmAuditRan": true,
  "pipAuditRan": true,
  "promptInjectionRan": true
}

Compare with similar skills

See how desktop-cc-gui compares with popular alternatives.

desktop-cc-gui vs cc switch

See comparison

desktop-cc-gui vs ui ux pro max skill

See comparison

desktop-cc-gui vs happy

See comparison

README.md

Frequently Asked Questions

What is desktop-cc-gui?

desktop-cc-gui is an open-source cli tools skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by zhukunpenglinyutong. Multi-engine AI coding desktop client (Tauri). Claude Code, Codex, Gemini, OpenCode, DeepSeek Harness and more in one GUI. It has 4,188 GitHub stars.

Is desktop-cc-gui safe to use?

desktop-cc-gui failed SkillsLLM's automated security scan, which flagged one or more high-severity issues. Review the Security Report section carefully before using it.

How do I install desktop-cc-gui?

Clone the repository with "git clone https://github.com/zhukunpenglinyutong/desktop-cc-gui" and add it to your Claude Code skills directory (see the Installation section above).

What programming language is desktop-cc-gui written in?

desktop-cc-gui is primarily written in TypeScript. It is open-source under zhukunpenglinyutong on GitHub, so you can review or fork the full source.

Are there alternatives to desktop-cc-gui?

Yes. SkillsLLM lists many other CLI Tools skills you can browse and compare side by side. Open the CLI Tools category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh desktop-cc-gui against similar tools.

LLM Engineer for Beginners

Ship LLM features to production - prompts, RAG, structured outputs, evaluation

39 minBeginner

Comments (0)

to leave a comment.

No comments yet. Be the first to share your thoughts!

Related Skills

ECC

by affaan-m

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

256,066

Popular in CLI Tools

Top skills in this category by stars

claude-code-templates

by davila7

CLI tool for configuring and monitoring Claude Code

30,590

codex-keysmith petdex

Desktop CC GUI

English · 简体中文

![][github-contributors-shield] ![][github-forks-shield] ![][github-stars-shield] ![][github-issues-shield]

ccgui is an open-source multi-engine AI coding desktop client. In plain words: it brings command-line AI coding runtimes — Claude Code, Codex CLI, Kimi CLI, Grok CLI, Pi CLI, OMP CLI, and DeepSeek Harness (DSH) — into one graphical interface.

No more staring at a black terminal. Open ccgui, pick a project, and chat with AI to write code, fix bugs, and commit to Git. Streaming output, thinking traces, and tool calls are visible as they happen; token usage appears when the engine reports it.

The app is built with Tauri 2 + React 18 + TypeScript + Rust and runs on macOS, Windows, and Linux. Settings and state are persisted locally. Content sent to an AI provider follows the boundary of the channel you configured for that CLI.

What can ccgui do?

One client, seven AI engines

Registers runtime adapters for Claude Code, Codex CLI, Kimi CLI, Grok CLI, Pi CLI, OMP CLI, and DeepSeek Harness — pick the engine per session from the composer.
Provider channels are written to each CLI's own native config files (no parallel credential store), with curated presets for GLM, Kimi, DeepSeek, MiniMax, MiMo, Bailian, LongCat, OpenCode Go, OpenRouter, and more. Claude / Codex / Grok channels can be imported from CC Switch.
Pi-family engines (Pi / OMP) support API-key and OAuth sign-in flows from inside Settings.
Per-tab model and effort overrides: different tabs in the same window can run different models or thinking levels.
Session history survives restarts; the history scanner reads each CLI's native session files and keeps titles in sync.

A chat box designed for coding

Streaming replies are revealed per animation frame with cached syntax highlighting — long outputs stay smooth instead of re-parsing markdown on every token.
Thinking streams merge with the reply text, auto-fold when they settle, and expand to full text on demand.
Tool calls show as live rows with expandable parameters and results, including beautified Git Diff and Bash viewers and per-run completion metadata.
A Run Status Strip mirrors the engine's live progress (including todo snapshots), and a message anchor rail lets you jump between user messages.
Pasted images become attachments; file mentions are backed by a .gitignore-aware project file index; file links in replies handle URL-encoded paths and have a right-click menu.
Permission denials can be resolved inline by granting the engine extra directories; prompt history and an optional Codex Fast toggle live in the composer.

Not just chat — a full set of dev panels

File tree: virtualized, with Git status colors, nested-repository badges, context menus, and drag-and-drop — plus a built-in CodeMirror editor pane with Markdown preview.
Built-in terminal: a real PTY-backed terminal dock (xterm + WebGL), no need to switch windows.
Git panel: stage, commit, search branches, inspect diffs and history.
Command palette: one keyboard-driven box for the app's commands.

Plugin system

First-party plugin SDK (@ccgui/plugin-sdk) plus an in-app runtime, manager UI, and trust boundary.
Declarative plugins can add settings sections and config-driven UI without shipping frontend code; builtin app surfaces (including the settings page itself) are registered through the same extension points.
See docs/plugin-development-guide.zh-CN.md for the full authoring guide.

Settings, network, and updates

Proxy settings for the app and engine traffic.
LAN web access: serve the UI to other devices on your network over a token-authenticated WebSocket bridge, with a QR-code entry in Settings.
Workspace management: group projects and switch between them.
In-app auto-update (Tauri updater against GitHub Releases), a changelog dialog, and signed macOS builds.
Bilingual UI: Chinese and English.

Download

Grab the installer for your platform from the Releases page:

Platform	Installer
macOS (Apple Silicon, signed)	`aarch64.dmg`
Windows	`.exe` (NSIS)
Linux	`.AppImage`

After installing, open Settings, configure a provider channel for the CLI you want (or sign in), add a project folder, and start chatting.

Using DeepSeek Harness (DSH)

Install the DSH CLI on your machine and configure its models and API keys in DSH itself — not as a separate vendor preset inside ccgui.
In Settings → DeepSeek Harness, ccgui can adopt a running local dsh web host or auto-start one.
Select DeepSeek Harness in the composer engine picker. Chat runs through DSH's headless profile; models and credentials stay in DSH.

Getting it running (setup guide)

Want to build it yourself or contribute? Three steps.

Step 1: Prepare your environment

Tool	Version	What for
Node.js	20 or newer	Runs the frontend toolchain
pnpm	10 (pinned via `packageManager`)	Installs dependencies
Rust	stable (install via rustup)	Compiles the backend

Each OS also needs the standard Tauri prerequisites — see the official Tauri guide:

macOS: xcode-select --install.
Windows: Microsoft C++ Build Tools and WebView2 (Windows 11 ships with WebView2).
Linux: webkit2gtk and friends — copy the commands from the Tauri docs.

Step 2: Install dependencies

git clone https://github.com/zhukunpenglinyutong/desktop-cc-gui.git
cd desktop-cc-gui
pnpm install

Note: this is a pnpm workspace (the plugin SDK lives in packages/plugin-sdk); the lockfile is pnpm-lock.yaml.

Step 3: Start it

pnpm dev

A few tips:

The first launch compiles the entire Rust backend and can take a few minutes — go grab a coffee. Later launches use incremental builds and are fast.
The frontend dev server runs on port 1420.

Building installers

pnpm build:mac                 # macOS signed build (scripts/build-signed-macos.sh)
pnpm build:mac:skip-notarize   # same, skipping notarization

Windows and Linux installers are produced by the CI workflows under .github/workflows/ (release.yml, build-windows-artifact.yml).

How to work on the code (development guide)

Tech stack at a glance

Part	Technology
UI	React 18 + TypeScript + Tailwind CSS 4 + zustand
Build	Vite 6
Desktop shell	Tauri 2 (Rust backend: git2, rusqlite, portable-pty, axum)
Tests	Vitest (frontend) + cargo test (Rust)

Directory layout

desktop-cc-gui/
├── src/                    # Frontend code
│   ├── features/           # ★ Feature modules: chat / files / git / terminal /
│   │                       #   settings / plugins / commands / update / open-app
│   ├── components/         # Shared UI components (incl. engine brand icons)
│   ├── i18n/               # zh + en locale bundles
│   ├── styles/             # Global styles
│   └── lib/ utils/         # Utility functions
├── src-tauri/              # Rust backend
│   └── src/                # engine/ (one module per CLI), history/, plugins/,
│                           # git.rs, terminal.rs, web.rs (LAN bridge), ...
├── packages/plugin-sdk/    # @ccgui/plugin-sdk — plugin authoring kit
├── tests/                  # Frontend integration-style tests (Vitest)
├── scripts/                # Build and packaging scripts
└── docs/                   # Plugin development guide, engine mode notes

The typical workflow for changing a feature

UI-only change: find the matching module under src/features/ and edit there. New components live inside that feature's own folder.
Needs backend support: add a #[tauri::command] in the matching src-tauri/src/ module and call it from the frontend via the Tauri API.
Changed any UI text: route it through i18n and keep both bundles (src/i18n/zh.ts, src/i18n/en.ts) synchronized — hardcoded UI text is not allowed.

Everyday commands

Command	What it does
`pnpm dev`	Start the full app (Tauri dev mode)
`pnpm build`	TypeScript check + frontend production build
`pnpm test`	Run the Vitest suite
`pnpm preview`	Preview the production frontend build
`cargo test --manifest-path src-tauri/Cargo.toml`	Run Rust tests

Writing tests

Frontend tests use Vitest — colocated xxx.test.ts(x) files next to the source, plus heavier suites under tests/.
Rust tests live in their modules as usual and run with cargo test --manifest-path src-tauri/Cargo.toml.

Coding rules

Not many rules, but each exists for a reason:

Run the big three before opening a PR: pnpm build (typecheck) and pnpm test green locally, plus cargo test if you touched Rust.
UI text must go through i18n: every user-visible string comes from src/i18n/, and both shipped locale bundles must stay synchronized.
Keep components close to home: new components start inside their own feature folder; promote to src/components/ only once they're genuinely reused across features.
TypeScript strict: don't paper over things with `an