A focused, fast workspace for Hermes Projects, Workflows, and Sessions.
One calm interface around Hermes—without the broad Python dashboard or lossy browser terminal input.
Focused HUE implementation resumed on 21 August 2026.
Development was paused on 25 July 2026 while the maintainer evaluated whether Hermes WebUI plus direct OpenCode/Codex delegation could satisfy the workflow without another application. That experiment exposed the durable unmet need now addressed here: reliable Hermes message delivery and Project-scoped Session organization in a purpose-built interface.
HUE is now a focused Hermes workspace client. HUE owns local Project and Workflow metadata plus reliable message-delivery state. Hermes ACP owns model/tool execution and Hermes Session persistence.
Implementation lives in app. The older broad personal-OS specification remains in the repository as historical design context, but ADR-0002 is the active scope decision.
HUE lets a user open a local Project, launch a reusable Workflow, and create or resume reliable Hermes Sessions whose complete messages survive retries and reconnects.
- Start with VISION.md.
- Open the Astro/Starlight documentation website and its embedded interactive specification, or run the docs and workspace locally with
make dev. - Review the specification in order:
- Status, labels and review protocol
- Problem, frustrations and product principles
- Product experience and user journeys
- Information architecture
- Spaces, sessions, knowledge and source ownership
- UI specification and screen wireframes
- Target system architecture
- Projects, context and layered memory
- Orchestration, workers and adaptive routing
- Tools, permissions and computer use
- Data model, events and service contracts
- Security, privacy and trust
- Quality, evaluation and observability
- Deployment and operations
- Milestones and implementation sequence
- Decision register
- Accepted frontend ADR: SvelteKit + shadcn-svelte
- Accepted focused workspace ADR: Bun + Hermes ACP
- Glossary
- Notifications, attention and delivery
| Label | Meaning |
|---|---|
| TBI | Target behavior is specified but not implemented. |
| TBD | A decision is still open; implementation must not silently choose. |
| SPEC | Documentation exists and is reviewable; this does not imply product implementation. |
| POC | A disposable proof was built to answer a named question. |
| IMPLEMENTED | Code exists and acceptance evidence is linked. |
| VERIFIED | The implemented behavior passed its documented verification gates. |
The canonical status rules live in docs/00-status-and-review.md.
HUE/
├── Makefile # starts the complete development workspace
├── app/ # SvelteKit/Bun Hermes workspace
├── docs/ # Astro app, specification, ADRs, roadmap, and spikes
├── prototype/ # canonical clickable UI wireframe source
├── VISION.md # stable product north star
└── .github/workflows/ # verified GitHub Pages deployment
The canonical product Markdown remains in VISION.md and docs/. docs/scripts/prepare_site.py projects those files into Starlight at build time, rewrites their internal links, and copies the prototype and roadmap data. Generated projections are ignored by Git so the website cannot become a second hand-edited source of truth.
bun install
make dev # app at :4010/ and documentation at :4010/docs/
bun run --cwd docs verifyThe production site is deployed to ctwhome.github.io/HUE by GitHub Actions after every verified push to main.
- Exactly three user-facing product objects: Projects, Workflows, Sessions.
- Projects are trusted working-directory boundaries; Workflows are reusable Project-scoped Hermes prompts; Sessions are Hermes ACP conversations.
- The browser sends complete message envelopes, never PTY keystrokes.
- HUE persists an envelope before acknowledging it, deduplicates client retries, and exposes monotonic reconnect cursors.
- Unknown delivery remains visibly unknown and is never auto-retried.
- HUE never writes Hermes'
state.dbdirectly and never silently grants ACP permission requests. - Data remains local by default in HUE SQLite plus the user's existing Hermes profile.
The canonical source is:
The GitHub copy is generated from those files so the plan and implementation tracker cannot drift silently.
TBD-019: The open-source license has not yet been selected. Until a license is explicitly adopted, this repository is source-visible but no reuse rights are granted by implication. The decision must balance ecosystem adoption, commercial embedding, contributor expectations and protection against closed hosted extraction.