Claude Code Haha
A cross-platform desktop workspace for Claude Code and multi-model coding tasks.
Per-dimension scores and reasoning
Evidence shows permission modes, GUI approval, undo, code signing policy, and privacy docs, but lacks implementation details or security audit. Deductions: least privilege, user confirmation, data flow transparency, sensitive data handling, dependency security, external effects, rollback, and source attribution are only partially supported, lacking in-depth evidence.
Extensive test scripts and test files indicate attention to consistency, but no test results or coverage data provided. Many dependencies, but no availability guarantees. Failure messages: troubleshooting docs exist, but no specific error handling examples. Deductions: dependency availability and failure messages insufficiently evidenced.
Multi-platform, multi-model, multi-IM integration, broad scenarios. Capability boundaries documented (permission modes, feature list), but no explicit limitations. Trigger precision: command reference and env docs, but no specific trigger conditions. Environment fit good, multi-platform support. Deductions: capability boundaries and trigger precision insufficiently evidenced.
Information architecture clear, docs directory and feature list. Install notes detailed, including download, configuration, and signing. Naming stable, but version number anomalous (999.0.0-local). Examples and FAQ present, but known limitations not explicitly listed. License MIT, but copyright year 2026 may be inaccurate. Versioning changelog not provided. Maintenance responsibility by author, but not explicit. Deductions: naming stability, known limitations, versioning changelog, and maintenance responsibility insufficiently evidenced.
Output usability high, rich features and docs. Marginal value high, multi-model, multi-platform support. Cost-benefit: sponsors and donation options, but no pricing or cost analysis. Deductions: cost-benefit insufficiently evidenced.
Claims supported by docs, but no traceable links or evidence. Cross-source corroboration limited, only internal docs. Fact-inference separation unclear, some claims may be inferred. Deductions: claim traceability, cross-source corroboration, and fact-inference separation insufficiently evidenced.
- Anomalous version number (999.0.0-local) may indicate unreleased state.
- Copyright year 2026 may be inaccurate.
- Many dependencies, but no security audit or vulnerability scanning evidence.
- Security features like permission modes and data flow transparency lack implementation details.
- No explicit list of known limitations.
What does this agent do, and when should you use it?
Claude Code Haha is a desktop Claude Code workspace for macOS, Windows, and Linux, with a source-run CLI path. Its Electron and React interface brings sessions, project switching, branch and Git Worktree launch, file changes, and syntax-highlighted diff review into one workspace. Users configure a model provider, API key, and default model, with documented sign-in or configuration paths for Claude, ChatGPT, Grok, several presets, LM Studio, and Ollama. The app also documents Computer Use, phone-browser H5 access, IM relays, scheduled tasks, usage statistics, a skill marketplace, and task-aware desktop pets. It fits developers who want a graphical control surface for local coding-agent sessions and isolated worktrees rather than a terminal-only workflow.
In the desktop app, a user creates or switches projects and sessions, selects a repository branch, then chooses the current working tree or an isolated Worktree. The workspace lists changes from the current turn; users can open files for syntax-highlighted diffs or undo the entire turn. Five permission modes let users approve risky commands, tool calls, and follow-up questions in the GUI, while Computer Use can take screenshots, click, type, and control desktop apps after authorization. The skill marketplace discovers, previews, and installs third-party skills from ClawHub / SkillHub with source and safety status, and scheduled tasks run in their own sessions. The documented source CLI flow runs bun install, cp .env.example .env, and ./bin/claude-haha.
- A Claude Code user managing several repositories and sessions who wants to inspect task progress and tool activity in one desktop workspace.
- An engineer working across branches who wants to choose between the current tree and an isolated Git Worktree before launching a task.
- A technical lead reviewing agent edits who needs file-by-file syntax-highlighted diffs and the option to undo an entire turn.
- A developer following a long-running task away from the desk who wants to continue a session or approve actions through H5, Telegram, Feishu, WeChat, DingTalk, or WhatsApp.
- A team member configuring coding models across hosted and local options, including Claude, ChatGPT, Grok, LM Studio, and Ollama.
What are this agent's strengths and limitations?
- Combines session management, project navigation, branch/Worktree selection, and file-level diff review in a cross-platform desktop workspace.
- Offers five permission modes and GUI approval for risky commands, tool calls, and follow-up questions.
- Documents paths for Claude, ChatGPT, Grok, multiple provider presets, and local-model options through LM Studio and Ollama.
- H5 remote access plus Telegram, Feishu, WeChat, DingTalk, and WhatsApp relays support mobile task follow-up and approvals.
- Computer Use, scheduled tasks, the skill marketplace, and the session activity panel extend the workflow beyond a standard terminal session.
- The desktop app uses Electron; the source CLI explicitly requires Bun, and Worktree usage depends on a Git workflow.
- Initial use requires a model provider, API key, and default model; provider pricing and quotas are not documented.
- Computer Use can control desktop applications; despite authorization requirements, users must choose permission modes carefully.
- Unsigned temporary macOS builds and Windows installers can require extra operating-system security approval.
- The marketplace installs third-party skills; source and safety status are shown, but the materials do not describe a separate audit guarantee for every skill.
How do you install or deploy this agent?
Desktop app: download the macOS, Windows, or Linux installer from GitHub Releases. On first launch, configure the model provider, API key, and default model in Settings. Public macOS releases require signing and notarization; draft or unsigned temporary builds may need one-time manual approval. Unsigned Windows installers may trigger SmartScreen; select “More info” and then “Run anyway.” Source CLI: install Bun, then run bun install, cp .env.example .env, and ./bin/claude-haha; configure provider credentials in .env.
How do you use this agent?
In the desktop app, first set the model provider, API key, and default model, then create or open a project and session. When starting work, choose a branch and either the current working tree or an isolated Worktree; review resulting workspace diffs file by file and undo the turn when necessary. For remote follow-up, scan the QR code to continue in a phone browser or pair a supported IM channel for conversation, project switching, and approvals. For the source CLI path, configure .env and run ./bin/claude-haha.
How does this agent compare with similar options?
The materials name cc-switch as a reference for model-provider configuration. Claude Code Haha's documented scope additionally includes desktop sessions, Worktrees, diff review, remote access, and Computer Use.