cloud-sessions 0.2.3

Fixes #1: list showed only the sessions tracked on this computer, and an empty first run gave no guidance.

• list (and /cloud-list, MCP cloud_list) now shows the sessions of your account by default when you allowed the Claude Code login (cloud-sessions auth use-claude-login): title, state, repository, last activity and link, newest first. The routines of the account, with their newest runs, are a second section (routines).
• list --tracked keeps the old view: only the sessions tracked on this computer, with no request to the API. list --unofficial stays accepted: the account view plus the raw API body (remote); it still fails when the account list fails.
• Each state says what to do next, in a hint field and in the text output. Login not allowed: "cloud-sessions auth use-claude-login (asks for a typed yes)". No sessions: how to start one (/cloud-start, claude --cloud) or track one (/cloud-track).
• When the account list cannot be read, list shows the tracked sessions and one fallback line with the reason and the fix. A routines failure is routines_error; it does not fail the list.
• The account list reads every page: the API sends 20 sessions a page with next_cursor, and list follows it (?cursor=) up to a safety cap of 50 pages or 1000 sessions (truncated says when the cap was reached). An error on a later page keeps the pages read so far and adds one partial line. routines and the routines section follow pages the same way. list --unofficial returns all pages in remote.data.
• A tracked session that is also in the account list shows once, with its title. A tracked session without a title shows its short id (session_ plus 10 characters), never "(untitled)".
• At a terminal, list prints text for a person; scripts, pipes and --json get JSON. The JSON keeps tracked (and remote with --unofficial) for existing callers, and adds view, sessions, routines, hint and fallback.
• No change to the login guarantees: without the opt-in, list reads no token and makes no request. The token goes only to https://api.anthropic.com (or a loopback test server). /cloud-start, /cloud-send, /cloud-allow and /cloud-stop stay user-only (disable-model-invocation).

cloud-sessions 0.2.2

• Fix (login): reading with Claude Code's login now honours CLAUDE_CONFIG_DIR. The login file is $CLAUDE_CONFIG_DIR/.credentials.json when that is set (and not empty), else ~/.claude/.credentials.json.
• Fix (login, macOS): when the keychain has no Claude Code login (no item, or a locked keychain over ssh), the login file is read instead. The keychain still comes first. The expiry check applies to both; an expired login is not sent and no token is printed.
• The lookup order is the same as in 0.2.1: Claude Code's login (after your opt-in), then the 0600 token file, then the keychain item of cloud-sessions.
• Docs: a "Control room" section. The control room that shows cloud sessions is in remote-sessions (remote-sessions control, from remote-sessions 0.3.0), with an image at docs/images/control-room.svg (placeholder data). The same paragraph is in README.zh-CN.md.

cloud-sessions 0.2.1

privacy: examples, fixtures and defaults no longer name the authors' machines, sessions or private repositories.