// OWNER · NanmiCoder · REPO SNAPSHOT
NanmiCoder
本地优先的跨平台 Claude Code / Agent 桌面工作台:多 Agent、Git Worktree、代码 Diff、技能市场、多模型、Computer Use、任务感知桌面宠物,并支持微信、飞书、钉钉、Telegram、WhatsApp 与 H5 访问。
//STAR HISTORY · 12M
Claude Code 泄露源码 - 本地可运行版本,新增跨平台桌面端软件补齐Computer Use(附带核心模块解析)
Claude Code Haha Claude Code Haha 基于 2026 03 31 从 Anthropic npm registry 泄露的 Claude Code 源码修复而来,现在主要是一个 桌面端 Claude Code 工作台 :把会话、多项目、分支 / Worktree、右侧代码改动、代码 Diff、权限审批、模型提供商、Computer Use、H5 远程访问、IM 接入和定时任务集中到一个 macOS / Windows APP 里。 桌面端预览 · 安装桌面端 · 桌面端亮点 · 赞助与合作 · 更多文档 桌面端预览 Claude Code Haha 的桌面端把会话、多项目、分支 / Worktree、右 It has reached 11,654 GitHub stars, written primarily in TypeScript.
Why now: Recent coverage — "GitHub - NanmiCoder/cc-haha: Claude Code 泄露源码 - 本地可运行版本,新增跨平台桌面端软件补齐Computer Use(附带核心模块解析) · GitHub" — alongside renewed developer interest is driving current visibility.
- 11,654 GitHub stars, 8,023 forks — verifiable at github.com/NanmiCoder/cc-haha.
- Primary language TypeScript.
- Licensed NOASSERTION.
- Third-party coverage: "GitHub - NanmiCoder/cc-haha: Claude Code 泄露源码 - 本地可运行版本,新增跨平台桌面端软件补齐Computer Use(附带核心模块解析) · GitHub".
Considerations: At roughly 2 months old, it's early — the architecture and maintenance cadence haven't been battle-tested yet.
EARLY MOMENTUM · Research: Adoption is real but cross-source confirmation is thin — a short hands-on trial (TypeScript) will tell you more than the metrics.
Sources: NanmiCoder/cc-haha on GitHub · Project homepage · Claude Code Haha:基于泄露源码的本地增强版AI 编码平台 · NanmiCoder/cc-haha: Claude Code 泄露源码- GitHub
Methodology: synthesized from this project's own documentation, live GitHub data, third-party coverage, and multi-platform signal convergence — by AISO.tools.
// RELATED REPOS · CROSS-SOURCE OVERLAP
▌ FAQ · answers from the data spine
What is NanmiCoder/cc-haha?
Who maintains cc-haha?
What language is cc-haha written in?
When was cc-haha created? When was the last update?
How do I install cc-haha?
git clone https://github.com/NanmiCoder/cc-haha.gitThen follow the README in the cloned directory.
//COMMENTS · 0
Sign in to join the discussion