Files
hermes-ui/docs/chat-chain-changes
toor 4701bf0ad0 Phase 004: remove the desktop shell, website tooling, and bundled hermes CLI
- Drop all desktop/Electron branches, scripts, and UI (title bar, pets,
  desktop bridge); LAN endpoint kind is now web/custom only
- Replace the bundled hermes CLI with user-side installation: add
  GET /api/hermes/cli-status plus a HermesMissingView onboarding guide
- Remove the version-management UI (snapshots handled by git) and prune
  dead website/mcu/claude scripts and lockfile entries
2026-10-16 15:33:56 +08:00
..

Chat Chain Change Fragments

Add one Markdown fragment per PR when a change touches the Chat session chain, Agent Bridge, compression, or Group Chat runtime paths documented in docs/cli-chat-sessions.md.

Do not append new rows to docs/cli-chat-sessions.md. Keeping one fragment per PR avoids merge conflicts when multiple branches change the chat chain at the same time.

Use this shape:

---
date: YYYY-MM-DD
pr: 1234
feature: Short feature name
impact: One-sentence behavior impact
---

Optional extra notes.

If the PR number is not known yet, use pr: pending while the branch is local, then update that same fragment after the PR is opened.