CLI Tree

chatbrowser is the browser runtime metadata CLI. It discovers browser backends, registers profiles, registers local loopback CDP endpoints, and exposes session endpoints to higher-level tools. It does not own platform-account semantics and does not install dependencies.

Importable APIs are mapped in Interface Tree. Package boundaries are tracked in Capability Map.

Top Level

chatbrowser                  # ChatBrowser command-line entry
├── --help                   # Show CLI help and registered commands
├── --version                # Print the package version
├── --tree                   # Print the registered CLI tree with parameter signatures
├── --tree-brief             # Print command nodes and descriptions without signatures
├── doctor                   # Read-only package and dependency check
├── backend                  # Discover local browser backends
├── profile                  # Manage isolated browser profile metadata
├── session                  # Read registered browser sessions
├── connect                  # Register an existing local loopback CDP endpoint without taking ownership
└── disconnect               # Remove a local session record without closing external browsers

The top-level options use ChatStyle's shared Click tree runtime. Run chatbrowser --tree to read back the registered tree with parameter signatures, or chatbrowser --tree-brief to keep command nodes and descriptions while omitting signatures. Both outputs use chatbrowser as the root. This page must not list unimplemented launch or extension subcommands as available commands.

doctor

chatbrowser doctor --output text|json

doctor is read-only. It reports the package version, ChatBrowser metadata home, chatstyle / chatenv dependency versions, optional ChatUp detection, and installs_dependencies=false to make the setup boundary explicit. ChatUp is no longer a hard dependency because its current releases require ChatStyle <0.2.0.

backend

chatbrowser backend list --output text|json
chatbrowser backend show <name> --output text|json
chatbrowser backend resolve <name> --output text|json

Known backend names:

• chrome-for-testing
• chromium
• chrome
• edge

These commands only inspect PATH; they do not install browsers. Missing backends should be handled by ChatUp or manual setup.

profile

chatbrowser profile list --output text|json
chatbrowser profile create <name> \
  [--path <profile-dir>] \
  [--backend chrome-for-testing] \
  [--label key=value] \
  [--output text|json]
chatbrowser profile show <name> --output text|json
chatbrowser profile path <name> [--kind root|downloads|logs|run]
chatbrowser profile status <name> --output text|json

A profile is an alias and path registration for a browser-state container. It is not a platform account. ChatBrowser stores only non-sensitive metadata: name, path, default backend, non-sensitive labels, and timestamps; sensitive label keys are rejected.

connect / disconnect

chatbrowser connect \
  --cdp-url http://127.0.0.1:9229 \
  --as-session-name <session-id> \
  [--profile <profile-name>] \
  [--output text|json]

chatbrowser disconnect <session-id> --output text|json

connect only registers an existing local loopback CDP endpoint (http://127.0.0.1:<port>, http://localhost:<port>, or IPv6 localhost; userinfo, paths, query strings, and fragments are rejected) with owned=false; disconnect removes ChatBrowser's local session record and does not close external browsers.

session

chatbrowser session list --output text|json
chatbrowser session show <session-id> --output text|json
chatbrowser session endpoint <session-id> --output text|json

session endpoint is the main integration point for upper layers such as ChatPost and Wechatsync.

Status Contract

Status	Meaning
Implemented	Command, Python function, and tests exist
Verified	Covered by local tests, CLI smoke, CI, or real-service practice
Planned	Keep only boundary notes; do not write operation tutorials before implementation