How to use Claude Code: install and sign in, verify it can see your repo, then add Clash Verge when you are in a network that blocks Anthropic. A working claude.ai tab does not mean the CLI path works.
Proxy deep-dive: Claude Code proxy setup. Web/Desktop: Claude.ai / Desktop. Sibling CLI: How to use Codex CLI.
The one mistake everyone makes
You open claude.ai in the browser, it works, so you assume the CLI is fine. It isn’t. The browser uses the system proxy you configured; the terminal runs in a different network context and often ignores it. Prove the CLI separately before blaming the model or your key.
Good fits vs bad fits
| Scenario | Good | Avoid |
|---|---|---|
| Scoped code edits | Yes | Huge deletes without Git |
| Running tests from logs | Yes | Pasting production secrets into prompts |
| China → Anthropic | Needs proxy | Assuming system proxy covers CLI |
Install and sign-in
- Install from Anthropic’s current official instructions.
- Open a new terminal after auth or env changes.
-
cdinto the Git root before the first task. - Ask a read-only question so you know it sees the right tree.
This site distributes Clash Verge Rev, not the Claude Code installer.
Daily five-step loop
- State file/directory boundaries.
- Define a verifiable check (test command or manual step).
- One concern per turn.
- Review the diff yourself before commit.
- On repeated timeouts, stop and fix network—do not rotate models blindly.
When Clash Verge is mandatory
Timeouts with a healthy browser usually mean the shell bypasses the proxy. Enable Tun or export proxies per the proxy guide, open a new terminal, and confirm traffic on the connections page.
Vs Cursor and Codex
Share one Clash install if you want; do not share one acceptance run. Debug one CLI at a time. Cursor: Cursor proxy. Codex usage: How to use Codex CLI.
Wrap-up
Download the client from the download center. For AI-wide Tun patterns see Tun for AI tools.