c2cd615824
The site had drifted from the product. Every screenshot predated the v0.5.0 UI redesign, the reading experience shipped no search and no syntax highlighting, and a third of the pages were internal process artefacts — migration task lists addressed to agentic workers, a release runbook, a proposal marked "historical". Reorganise around the only two people who read this: someone getting the desktop app running for the first time, and someone reading the source. Five sections replace nine — start / desktop / im / cli / internals — and the pages that served neither reader are gone. Site rewrite: - Palette lifted from the desktop app's 「纸·墨·印」 themes, so the site and the product read as one thing. Light mirrors 纯白, dark mirrors 墨夜, and dark mode exists at all now. - Fonts are self-hosted. The old @import from Google Fonts is unreachable from mainland China, which left every heading in a fallback serif; it also only requested weight 600 while the CSS asked for 900, so Latin and CJK in the same heading disagreed. - Docs were shipped as one 968KB manifest downloaded on every page view. Split into a 32KB index plus one lazily imported chunk per page; the entry bundle is now 101KB gzipped. - Add search, syntax highlighting, per-route meta with canonical and hreflang, a sitemap, and an error boundary. Replace the 44vh mobile sidebar with a drawer. - Image dimensions are read at build time and written into the tag, so lazy images reserve their space instead of collapsing. Screenshots are recaptured from a real v0.5.0 build against a clean demo project, with tokens, QR codes and paired accounts redacted. The previous set is deleted rather than kept alongside. Routes follow file paths, so the restructure would have broken every inbound link; 37 old paths redirect, in both languages. The PR policy gate and CODEOWNERS also hardcoded docs/guide/contributing.md. Verified: check:docs 78 pages / 323 links / 0 problems, check:policy 127 pass. Walked every route at 1440 and 390 in both themes for overflow, contrast, keyboard reachability and focus management.
5.4 KiB
| title | nav_title | description | order |
|---|---|---|---|
| Download and install | Install | Installers for macOS, Windows, and Linux, plus what to do when the OS blocks them. | 1 |
Download and install
Install and go. You don't need Node.js, Python, or Claude Code — the CLI engine and the ripgrep binary used for file search are both bundled inside the installer.
Pick the right package
Everything lives on GitHub Releases. Choose by operating system and CPU architecture:
| Your system | Download |
|---|---|
| macOS, Apple Silicon | Claude-Code-Haha-<version>-mac-arm64.dmg |
| macOS, Intel | Claude-Code-Haha-<version>-mac-x64.dmg |
| Windows x64 | Claude-Code-Haha-<version>-win-x64.exe |
| Windows ARM64 | Claude-Code-Haha-<version>-win-arm64.exe |
| Linux x64 | Claude-Code-Haha-<version>-linux-x86_64.AppImage or -linux-amd64.deb |
| Linux ARM64 | Claude-Code-Haha-<version>-linux-arm64.AppImage or -linux-arm64.deb |
Not sure which architecture you have? On macOS check the chip listed in "About This Mac"; on Windows check the system type under Settings → System → About. Don't guess from the brand of the machine.
The .blockmap and latest*.yml files are used by the app's own updater. You don't need to download them.
macOS
- Open the DMG.
- Drag Claude Code Haha into Applications.
- Launch it from Applications.
If macOS says the app is damaged
Nothing is actually damaged. macOS quarantines anything downloaded from the web and refuses to launch it without an Apple signature — but it words the error as "damaged", which is thoroughly misleading. Signed and notarized releases skip this entirely; if you have an unsigned build, use one of the two routes below.
Option 1: the official script (recommended)
Download install-macos-unsigned.sh from the same Release into the same folder as the DMG (Downloads, for example), then run:
cd ~/Downloads
bash install-macos-unsigned.sh
The script picks the DMG matching your architecture, mounts it, installs the app into /Applications, strips the quarantine attribute, and launches it. Any existing install is moved to the Trash first rather than overwritten in place.
Option 2: clear the quarantine flag yourself
If the app is already in Applications:
xattr -dr com.apple.quarantine "/Applications/Claude Code Haha.app"
Only do this for packages you have confirmed came from this repository's Releases. Never bypass Gatekeeper for software of unknown origin.
Windows
- Fully quit any running copy of the old version, including the system tray icon.
- Double-click the
.exe. - Don't right-click and choose "Run as administrator" — the installer is per-user, and running it elevated puts your data directory in the wrong place.
Unsigned packages trigger a SmartScreen warning. Once you've confirmed the file came from this repository's Releases, click "More info" → "Run anyway".
When upgrading in place, the installer inspects user data in the old install directory. If it reports that the program is still running, quit the main window and the tray icon, give the background sidecar, terminal, and IM adapter processes a few seconds to exit, then run the installer again. Don't delete the old install directory by hand first.
Linux
AppImage (no installation, just run it):
chmod +x Claude-Code-Haha-<version>-linux-x86_64.AppImage
./Claude-Code-Haha-<version>-linux-x86_64.AppImage
If it fails with a FUSE-related error, install the runtime: sudo apt install libfuse2 on Ubuntu 22.04 and earlier, libfuse2t64 on 24.04 and later.
deb (installs into your application menu):
sudo apt install ./Claude-Code-Haha-<version>-linux-amd64.deb
On ARM64 machines, use the corresponding linux-arm64 file.
Running from source
If you want to modify the code, debug the engine, or just use the CLI in a terminal:
git clone https://github.com/NanmiCoder/cc-haha.git
cd cc-haha
bun install
cp .env.example .env
./bin/claude-haha
Requires Bun and Git. This runs the CLI only; for building the desktop app and configuring the local server, see Command line.
Updating
In-app updates (recommended). Open Settings → About → App Updates and click "Check now". It compares your installed version against the latest GitHub Release, downloads the new build, and offers "Install and restart".
Before updating, stop any running sessions and save uncommitted work.
If the download stalls, you probably can't reach GitHub. The same panel has an "Advanced update proxy" setting where you can switch to the system proxy or enter a local HTTP proxy address (http://127.0.0.1:7890, for instance). This proxy only affects the app's own update downloads — it has no effect on model requests.
Manual replacement. Download the new installer from Releases and repeat the steps for your platform. Sessions, provider configuration, skills, agents, and memory live under ~/.claude, not in the application directory, so installing over the top doesn't touch them.
:::warning The installer's data protection is not a backup. Keep your own copy of anything you can't afford to lose. :::
Next
Go to Connect a model. Until a model is connected, the app opens but can't send a single message.
If it won't install or won't open, see Won't install, won't open, won't connect.