B — Some risk signals Graded October 16, 2026Minor concerns worth a quick check.Based on public adoption and transparency signals as of October 16, 2026. Our opinion, not a code audit or security guarantee.
App connector · Developer tools, Communication
cc-haha
本地优先的跨平台 Claude Code / AI Agent 桌面工作台:多 Agent 协作、Git Worktree、代码 Diff、技能市场、多模型、Computer Use、桌面宠物;支持微信、飞书、钉钉及 H5 等远程访问。 | Local-first Claude Code / AI Agent desktop workspace: multi-agent teams, Git worktrees, diffs, skills marketplace, multi-model, Computer Use, task-aware desktop pets; remote via WeChat, Feishu, DingTalk, Telegram, WhatsApp & H5.
Bottom line: Signal-based grade (4/7 points): very widely starred on GitHub, public source code. This reflects adoption and transparency, not a code audit.
- Popularity score
- 47/100
- Rank
- Not ranked: outside the 500 most popular tools
- GitHub stars
- 15k
What it does
cc-haha is a local-first desktop workspace for Claude Code and AI agents that enables multi-agent collaboration, Git integration with worktrees and diffs, a skills marketplace, multi-model support, and Computer Use capabilities. It includes task-aware desktop pets and supports remote access via WeChat, Feishu, DingTalk, Telegram, WhatsApp, and web interfaces.
Who it’s for
Developers and teams building with Claude and multi-agent AI systems who want a unified desktop environment with local-first control. Builders in China and Asia may particularly value native integrations with WeChat, Feishu, and DingTalk for team collaboration.
Copy-paste setup
Check these steps against the project’s own instructions before running anything.
Verify against the repo README at https://github.com/NanmiCoder/cc-haha (opens external site) for precise installation steps. The project appears to be a desktop application rather than a standard npm package, so installation likely involves cloning the repository and following platform-specific build instructions rather than a simple npx command.
Risks
- Remote access via multiple messaging platforms (WeChat, Feishu, DingTalk, Telegram, WhatsApp) expands attack surface and credential exposure risk if keys/tokens are not properly isolated
- Computer Use capability grants agents significant system-level permissions; unclear scoping of what actions agents can perform on the host machine
- Local-first architecture with remote access may create tension between data privacy claims and actual data transmission practices—verify what telemetry or logs are sent externally
- Skills marketplace introduces supply-chain risk if third-party agent skills are not sandboxed or verified; prompt injection possible through untrusted skill definitions
- Desktop pet feature and multi-modal support increase code complexity surface area for vulnerabilities; maintenance velocity should be monitored
How to stay secure
Least-privilege permissions
- Restrict agent access: Limit what actions agents can perform on your computer. Only grant "Computer Use" (ability to control your screen/keyboard) to trusted agents; disable it for experimental or third-party tools.
- Isolate messaging account credentials: Store WeChat, Feishu, DingTalk, and other login tokens in a separate, encrypted vault. Never hardcode or share these credentials; rotate them monthly.
- Sandbox skills from the marketplace: Treat downloaded agent skills like app downloads—only install from verified publishers. Use a sandboxed test environment before running them on your main workspace.
- Separate user accounts for testing: Run new or untrusted agents under a limited computer user account (not your admin account) so they cannot access sensitive files or system settings.
Network isolation
- VPN or firewall rules for remote access: If using WeChat/Feishu/DingTalk remote control, restrict access to a corporate VPN or whitelist specific IP ranges. Do not expose remote endpoints to the public internet.
- Encrypt all messaging connections: Ensure all remote messaging platforms enforce end-to-end encryption. Verify that tokens and session data are transmitted over HTTPS only.
- Monitor outbound traffic: Use a network tool (like your firewall or packet sniffer) to confirm no unexpected data is leaving your computer to external servers. Especially check for telemetry or logs going to unmapped cloud services.
- Disable remote access when not needed: Turn off WeChat/Telegram/H5 remote access during sensitive work. Only enable the minimum messaging platforms required for your workflow.
Monitoring
- Review agent action logs weekly: Check what actions each agent performed (files accessed, commands run, data copied). Most MCP tools log this—look for unusual patterns like access to password managers or payment files.
- Audit skill installations and updates: Keep a list of installed marketplace skills and their last update date. Investigate any auto-updates or new versions that perform new actions.
- Track failed authentication attempts: Monitor failed login attempts on your messaging accounts. A spike may indicate someone is trying to gain remote access to your workspace.
- Set alerts for sensitive file access: Configure your OS to alert you if agents access critical folders (passwords, financial data, source code repositories). Flag any unexpected access immediately.
Red flags to watch for
- Agents requesting "full system access" or refusing permission scoping: Legitimate agents should accept restrictions. Any tool demanding unrestricted Computer Use privileges is suspicious.
- Skills updating themselves automatically without your approval: Third-party skills should not auto-update. Any self-modifying behavior suggests potential malware or supply-chain compromise.
- Unexpected network traffic or battery drain: If your computer is slow or battery depletes quickly, agents may be running hidden processes or exfiltrating data in the background.
- Credential or token prompts appearing unexpectedly: If the workspace suddenly asks for your WeChat password, API keys, or bank login, do not enter it—this may be a prompt injection attack from a compromised skill or agent.
Alternatives
- OpenInterpreter — open-source Python environment for agentic code execution with similar Computer Use capabilities
- Cline (Claude in the terminal) — lighter-weight Claude agent integration focused on CLI-first workflows
- Cursor or GitHub Copilot extensions — IDE-integrated AI agents with narrower system access scope
- LangChain / LlamaIndex agent frameworks — programmatic, developer-controlled agent orchestration without desktop UI lock-in