feat(webui): opt-in local browser gateway with managed update lifecycle #54

Merged

karsten merged 2 commits from feat/local-webui into main 2026-11-06 15:33:55 +00:00

Conversation 1 Commits 2 Files changed 16 +2147 -2

karsten commented 2026-11-06 15:23:15 +00:00

Owner

Copy link

Summary

• Standalone local-loopback GatewayModule v1, plus optional settings-tool PluginModule.
• Persistent multiple chats, streaming, safe Markdown/code, search, rename/export and responsive layout.
• Operator/agent-configurable declarative panels/actions and explicitly installed trusted UI modules.
• Host-owned ingress, commands, authority and durable delivery; no parallel agent runtime.
• Foreground-owned update contract, synchronous fencing, socket/refresh/write draining, cleanup failures and restart coverage.
• Extend native compatibility CI to build/test the separate WebUI directory and actual Core host integration.

Local verification

• 22 Node tests passed; Chromium regression suite passed; bundle build passed.
• WebUI npm audit: no reported findings.
• Actual Core PluginHost/GatewayManager/Harness integration passed: deduplication, idle/busy admission, lease fencing, retry, open-SSE shutdown.
• Core onboarding candidate suite: 1584 passed, 1 existing skipped Slack fixture, 0 failures. Remote exact-head CI/review still required.

Boundaries

The separate terminal-conversation catalog and unrelated TUI/session changes are excluded.
No network authentication or fleet deployment: listener remains IPv4 loopback only.
Built browser assets must accompany the installed plugin; current Core Dockerfile/materializer does not package this directory automatically.
No Service/Ingress or unauthenticated network exposure. See webui/README.md and webui/RELEASE.md.

Canonical source publication and fleet artifact packaging/activation remain separate steps through the existing owners. Do not treat this source PR as a completed homelab rollout.

Exact submitted head: 52fc295d94edaf4c819f4d236dabd8e177ea5efe.

## Summary - Standalone local-loopback GatewayModule v1, plus optional settings-tool PluginModule. - Persistent multiple chats, streaming, safe Markdown/code, search, rename/export and responsive layout. - Operator/agent-configurable declarative panels/actions and explicitly installed trusted UI modules. - Host-owned ingress, commands, authority and durable delivery; no parallel agent runtime. - Foreground-owned update contract, synchronous fencing, socket/refresh/write draining, cleanup failures and restart coverage. - Extend native compatibility CI to build/test the separate WebUI directory and actual Core host integration. ## Local verification - 22 Node tests passed; Chromium regression suite passed; bundle build passed. - WebUI npm audit: no reported findings. - Actual Core PluginHost/GatewayManager/Harness integration passed: deduplication, idle/busy admission, lease fencing, retry, open-SSE shutdown. - Core onboarding candidate suite: 1584 passed, 1 existing skipped Slack fixture, 0 failures. Remote exact-head CI/review still required. ## Boundaries The separate terminal-conversation catalog and unrelated TUI/session changes are excluded. No network authentication or fleet deployment: listener remains IPv4 loopback only. Built browser assets must accompany the installed plugin; current Core Dockerfile/materializer does not package this directory automatically. No Service/Ingress or unauthenticated network exposure. See `webui/README.md` and `webui/RELEASE.md`. Canonical source publication and fleet artifact packaging/activation remain separate steps through the existing owners. Do not treat this source PR as a completed homelab rollout. Exact submitted head: `52fc295d94edaf4c819f4d236dabd8e177ea5efe`.

karsten added 1 commit 2026-11-06 15:23:15 +00:00

feat(webui): add opt-in local browser gateway with managed update lifecycle 52fc295d94

karsten referenced this pull request from harness/core 2026-11-06 15:23:16 +00:00

feat(setup): WebUI and Matrix onboarding with safe starter defaults #295

karsten added 1 commit 2026-11-06 15:29:26 +00:00

ci: install Python and flock required by Core session ownership tests 5e62ed258a

karsten commented 2026-11-06 15:29:47 +00:00

Author

Owner

Copy link

CI follow-up: the first exact-head run failed because the compatibility container lacked Python 3 required by current Core OS session locks (14 failing cases all report that missing prerequisite). Commit 5e62ed258a77dd9c18e159280e5a7f98426d5a0b installs python3 and util-linux; no tests or checks were removed, and no Core/plugin behavior was changed. A fresh exact-head run is now required.

CI follow-up: the first exact-head run failed because the compatibility container lacked Python 3 required by current Core OS session locks (14 failing cases all report that missing prerequisite). Commit `5e62ed258a77dd9c18e159280e5a7f98426d5a0b` installs `python3` and `util-linux`; no tests or checks were removed, and no Core/plugin behavior was changed. A fresh exact-head run is now required.

karsten merged commit a03e5d2622 into main 2026-11-06 15:33:55 +00:00

karsten referenced this pull request from a commit 2026-11-06 15:33:57 +00:00

Merge pull request 'feat(webui): opt-in local browser gateway with managed update lifecycle' (#54) from feat/local-webui into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

harness/plugins!54

No description provided.