KuiyiGao/deepcrew

# Leading a deepcrew team

This session is the leader. Members are stock Claude Code processes on the provider's model; they share the project and each writes only inside its own region. Run every command from the project directory, as its own command (no `cd` or redirection around it). One session leads one team; `deepcrew stop --all` ends it.

## Set up
Always in this order:
1. Run `deepcrew up`. It asks nothing: its first line is the page address.
2. Open that address in the browser pane right away (Claude desktop app; elsewhere give the link) and write it in the chat too. Tell the user: the API key and the settings are set on that page; the key stays on this computer and goes only to the provider.
3. Show the block as printed (`deepcrew status` prints it again). Its `prices` line says what the provider charges now and until when (UTC); `deepcrew prices` lists the coming changes, so the user can choose to start now or at a cheaper hour. If it has a `setup` line, run `deepcrew inbox --wait 600` in the background and start no member until it reports `setup: done`.
- The page shows the team panel (members, their cost, Rest crew and Resume crew), the key, the presets and members' requests; the user answers requests there and your inbox says when they did. Its Team Call tab shows who speaks and what members report, its Monitor tab the team as a network, its tasks as a table and what it costs; beside both, a chat where the user writes to you, to a member or to everyone, and the requests waiting for the user.
- The user may follow the team on the page rather than in the chat: put everything you tell the user there too, with `deepcrew send user "..."` (the same words, short and plain), in the language the user reads replies in (`deepcrew lang`; `deepcrew lang NAME` when they ask for another; the crew keeps working in English).
- Settings belong to the user: the page, or `deepcrew config preset NAME ...` from the command line (a setup: standard, crowd, strong or locked; or a strength, a size and a scope: strength fast is the default; sizes solo, pair, squad, crowd, large; at most 32 members). Both update the running team at once.
- Never ask for, read or print an API key. A user who prefers a terminal can run `deepcrew auth set PROVIDER` there instead (`deepcrew auth set deepseek` for the default).

## Plan