CLI reference by side effect
These nodes match the registered chatglance --tree-brief. For exact arguments, run chatglance --tree or chatglance <group> <command> --help on the installed version. Do not conflate reads, candidate writes, and runtime mutations.
Access and page generation
chatglance
├── access
│ ├── render-public
│ └── render-single-origin-optional-login
├── projects
│ ├── collect
│ ├── render-page
│ └── update-config
├── sites
│ ├── collect
│ ├── export-covers
│ ├── render-page
│ └── update-config
└── servers
├── candidates
├── collect
├── render-page
├── update-config
└── validate-refresh
access render-single-origin-optional-login writes a private single-origin candidate to an explicit path. access render-public remains a detached public offline config/inventory candidate, not a recommended second-site deployment. projects collect gathers metadata, render-page creates a page fragment, and update-config writes a config copy. Server and site collection uses explicit inventories; never place the full project inventory in anonymous assets.
Refresh and runtime
chatglance
├── refresh
├── runtime
│ ├── controls
│ ├── adopt
│ ├── check
│ ├── history
│ │ ├── list
│ │ ├── prune
│ │ └── show
│ ├── init
│ ├── install
│ ├── import-env
│ ├── install-binary
│ ├── install-systemd
│ ├── instance
│ │ ├── configure
│ │ ├── init
│ │ ├── render-launchd
│ │ ├── set-login
│ │ └── show
│ ├── maintain
│ ├── maintain-managed
│ ├── paths
│ ├── render-portable
│ ├── render-systemd
│ ├── refresh-managed
│ ├── restart
│ ├── rollback
│ ├── serve
│ ├── start
│ ├── status
│ ├── stop
│ └── update
├── home
│ └── remove-widget
└── disks
└── root-only
refresh updates configured pages from existing runtime inventories; manual mode never redeems reset cards. runtime history list/show are read-only, while prune previews unless --apply explicitly removes confirmed-owned history. runtime init creates loopback configuration and empty snapshots only; install-binary requires a local archive and SHA256. render-portable prints or writes review units without registering them; serve and controls require explicit execution. runtime maintain may rewrite runtime config; legacy install-systemd and start change user-level units and require separate review. See Refresh and operations.
runtime instance init/configure/set-login/render-launchd preview by default. They create a private read-only runtime, disable or re-enable pages and enabled accounts in the same named profile, provision native Go login and render macOS review templates; --apply writes. instance show displays only non-secret selection and ownership. Instance refresh and serve use the same native runtime path and obey the saved manifest; extra pages, controls and maintenance writes are rejected. See named instance deployment.
Account limits and reset controls
Managed install, adopt, update, rollback, stop and restart default to dry-run; --apply/--yes authorizes writes/actions. start/status select managed behavior with --runtime-home, preserving legacy behavior otherwise. check reports validated binary/config ownership; refresh-managed and maintain-managed are real installed native unit entrypoints, not review-only renderers. See managed deployment for complete adoption/rollback and private-input contracts.
chatglance
└── account-limits
├── collect
├── control-serve
├── json
├── render-page
├── subscriptions
│ ├── add
│ ├── disable
│ ├── enable
│ ├── list
│ └── remove
└── update-config
subscriptions manages explicit CRS profile/account references through ChatEnv; mutations preview unless --execute persists them, and tracking does not change automatic-use policy. collect handles account usage and the reset calendar, selecting enabled subscriptions by default. control-serve is an authenticated local toggle endpoint. Scheduled reset execution requires explicit refresh --scheduled and per-account policy; rendering a page does not authorize consumption. Review access controls before using real accounts.