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.
3.8 KiB
| title | nav_title | description | order |
|---|---|---|---|
| Install and Run | Install and Run | Run the CLI from source - install dependencies, configure a provider, launch from any directory. | 0 |
Install and Run
The CLI is the core of Claude Code Haha — every desktop session runs one underneath. If you only want the graphical app, installing that is enough; see Download and install. The steps below are for people who want a terminal workflow, --print automation, or a source checkout to read and contribute to.
The CLI runs from source only. There is no separate installer for it.
Get the source
Install Git and Bun first, then:
git clone https://github.com/NanmiCoder/cc-haha.git
cd cc-haha
bun install
Configure a model provider
cp .env.example .env
Edit .env with at least one working authentication method, base URL, and model. A minimal Anthropic-compatible setup looks like this:
ANTHROPIC_AUTH_TOKEN=sk-example
ANTHROPIC_BASE_URL=https://provider.example.com/anthropic
ANTHROPIC_MODEL=provider-model
See Environment variables for what each variable means, how the authentication headers differ, and how to configure Azure and other protocols. If you already configured a provider in the desktop app, the CLI reuses it and you do not need a .env at all.
Never commit a real API key, and never paste one into an issue, a screenshot, or a diagnostics bundle.
Start and verify
macOS, Linux, or Git Bash:
./bin/claude-haha
./bin/claude-haha -p "Summarize the directory structure of this project"
Windows PowerShell or cmd:
bun --env-file=.env ./src/entrypoints/cli.tsx
Once you see streaming output and tool calls, the provider, the project directory, and the CLI are connected.
Run from any directory
./bin/claude-haha only works inside the checkout. Put it on your PATH and you can type claude-haha in any project directory — the CLI treats the current working directory as the project root.
On macOS and Linux, add this to ~/.bashrc or ~/.zshrc:
# Option 1: add to PATH (recommended)
export PATH="$HOME/path/to/claude-code-haha/bin:$PATH"
# Option 2: alias
alias claude-haha="$HOME/path/to/claude-code-haha/bin/claude-haha"
Reload the shell config:
source ~/.zshrc # or source ~/.bashrc
On Windows, add the same PATH line to ~/.bashrc under Git Bash:
export PATH="$HOME/path/to/claude-code-haha/bin:$PATH"
To verify, start it from a different directory and ask what the current directory is:
cd ~/your-other-project
claude-haha
Windows with a WSL toolchain
If claude-haha runs on Windows or Git Bash while Node, Python, uv, and bun live inside WSL, call them through WSL explicitly:
wsl -e bash -lc 'node --version && python3 --version'
When the CLI detects a wsl / wsl.exe invocation, it sets MSYS2_ARG_CONV_EXCL=* so Git Bash does not rewrite WSL paths such as /home/... into C:/Program Files/Git/home/....
To route Bash tool commands through WSL by default, set this before startup:
export CLAUDE_CODE_SHELL_PREFIX='wsl -e bash -lc'
Computer Use still controls Windows desktop apps, so CLI tools inside WSL do not need an entry in computer-use-config.json. If you only need the WSL toolchain and no desktop control, pass --no-computer-use or turn it off under Settings → Computer Use.
Next steps
- Command reference: flags, headless mode, and recovery mode
- Environment variables: the full list of authentication, model, and runtime variables
- Architecture overview: how the CLI, server, desktop shell, and adapters divide the work
- Contributing and quality gates: what to run before opening a PR