Files
pipelines/internal/author/skill/references/access.md
T
alan 526c19fc21 web: shared chat stars, pipeline mini graphs and agent questions
- Persist chat stars in the operator-session registry (chat_star) so every
  browser/device shows the same Starred group; migrate old local stars once.
- Add a compact pipeline graph shape to list responses and draw a lightweight
  list miniature; replace the cryptic id/version line with the stage count.
- Surface OpenCode form questions as a chat card (chat_answer), replay a
  pending form to late subscribers, and notify for background questions.
- Make the mobile dock's Search cell equal to every destination, keep the
  tab row visible with 100svh, and let Source use the full pane height.
- Let a fresh sign-in auto-connect to its own origin; use a Lax session cookie
  with Expires so Remember me survives app/link launches.
- Keep shipped starters and the skill agnostic: no repository paths, project
  areas or personal device commands; add Diagnose/Fix and Research starters.
- Refresh the installed skill and document the new browser conventions.
2026-10-20 03:11:37 +01:00

56 lines
2.1 KiB
Markdown

# Hosting, access and deployment
The browser client is `web/serve.mjs`: static files plus a `/connect` WebSocket
proxy and `/artifacts/` proxy to the Pipelines server. Plain `node serve.mjs` is
enough for local work.
## Password gate
`serve.mjs` refuses pages, assets, artifacts and `/connect` without a signed
session cookie. The password and signing secret live outside the repository:
`~/.config/pipelines/web-auth.json` (mode `600`), e.g.
```json
{ "password": "…", "secret": "…" }
```
The sign-in page is `/login`; **Remember me** keeps a 30-day cookie, otherwise
the cookie lives until the browser closes. Wrong passwords are throttled. Tests
that start their own `serve.mjs` set `PIPELINES_WEB_AUTH=disabled`; never put that
in a service.
Changing the password: edit the file, then restart the web service.
## Bind and exposure
For an untrusted network, keep the raw ports local:
- Pipelines server: `-addr 127.0.0.1:8080`.
- Web proxy: `--host 127.0.0.1` (reachable through Tailscale, not the LAN).
- OpenCode: `server.hostname = "127.0.0.1"` in `~/.config/opencode/opencode.json`.
Tailscale can terminate HTTPS for a tailnet-only name:
```sh
tailscale serve --bg --https=8443 http://127.0.0.1:8095
# https://<machine>.<tailnet>.ts.net:8443/
```
That gives a valid certificate and a secure context (service worker, installable
web app). Only tailnet devices can resolve the name; the password still applies
to the app and its WebSocket.
Keep the server and web proxy supervised by the platform's service manager so
they restart after a reboot. Name the service files for your installation; their
labels are local choices, not part of the protocol. The HTTPS proxy rule must
also survive a reboot.
## Before exposing anything
Check what listens beyond loopback (`lsof -nP -iTCP -sTCP:LISTEN`). The Pipelines
server and the agent harness are control APIs without their own login; bind them
to localhost and expose only the authenticated web proxy. If an app-managed
server cannot bind loopback, a host firewall or tailnet ACLs are the remaining
options. Unrelated operating-system services are outside this deployment.