Broker chat from an operator's own OpenCode endpoint and adopt existing sessions

Add an opt-in way to broker chat from an operator-supplied OpenCode service
instead of the instance the server spawns for itself, and a way to adopt a
session that already exists on that endpoint so it appears in chat_sessions and
can be continued from the app.

- Endpoint selection: the `-opencode-endpoint` server flag (defaulting to
  `PIPELINES_OPENCODE_ENDPOINT`) opts in; precedence is explicit flag >
  explicit environment > the endpoint recorded on a previous run, with the
  spawned instance as the default. opencode.OpenEndpoint validates the
  reference once (http(s), host, no userinfo/query/fragment/path), detects the
  backend from its own /api/info (v2) or /global/health (v1) contract, and
  requires a streamable text/event-stream event path. It owns no process
  (Close is a no-op) and never calls startServe; every failure names the
  endpoint and disables chat rather than silently falling back. An
  authenticated endpoint takes an optional password only through the private
  file PIPELINES_OPENCODE_ENDPOINT_PASSWORD_FILE, with
  PIPELINES_OPENCODE_ENDPOINT_USERNAME overriding the detected default.
- Persistence: the validated choice is recorded in an additive single-row
  server_settings table so a restart with no flag/environment reuses it; an
  unreachable recorded endpoint disables chat with a clear message and no
  fallback.
- chat_adopt: a new protocol request (ChatAdoptRequest) with handleChatAdopt in
  internal/server/chat.go. It refuses a nil broker/registry/payload and a
  blank or foreign-shaped id before any endpoint call, reads the endpoint via
  the shared Chat.Session (which reuses Sessions/decodeChatSessions), records
  through the existing RecordOperatorSession with the endpoint's directory and
  title verbatim, and echoes the adopted session plus its registry row like
  chat_create. A missing id is refused naming the id and records nothing; an
  endpoint record with an empty directory is refused rather than substituting
  the server's working directory or home.
- CLI: `pipelines chat-adopt <session-id> [--json]` (usage, notes, help
  inventory, dispatch) with docs/cli.md updated under Chat sessions.
- Autostart preserves the endpoint variables (and the password-file reference,
  never an inline secret) via serviceEnvironmentKeys.

Checks before committing:
- Package location: the change is user-facing chat behaviour, so the packaged
  authoring skill reference internal/author/skill/references/operations.md is
  updated in the same change (Brokered OpenCode chat section) with a dated
  verification-evidence entry and the not-deployed state. No new reference file
  is added, so internal/author/install.go's managed inventory is unchanged.
- Packaged templates: this repository packages no template set for this
  behaviour and none references the chat endpoint, so no template needs
  updating.
- Verification: `go build ./...`, `go vet` on the touched packages, `gofmt -l`
  clean and `go test ./...` all pass. The unit tests cover the endpoint
  validation/precedence, the adopt happy path and refusals, the recorded
  endpoint round-trip, the protocol round-trip and the CLI dispatch. The live
  scratch-server check against the operator's real endpoint was not run in this
  change.

Nothing unrelated is staged; docs left stale (README and other shared documents)
are not edited here and are for a single folding writer.
This commit is contained in:
2026-10-17 20:14:11 +01:00
parent 50af9dbc62
commit 1f75e4797e
20 changed files with 1027 additions and 33 deletions
+34
View File
@@ -314,6 +314,40 @@ sessions pipeline runs create. The protocol types are:
(currently 8). It is a dedicated request so the create dialog can load the
choices without first listing sessions; `chat_sessions` stays a pure session
list.
- `chat_adopt` takes a `session_id` that already exists on the configured
endpoint and records it in the operator session registry, using the endpoint's
own directory and title (never a guess or the server's working directory). The
response echoes the adopted session as `chat_session` and, like `chat_create`,
its registry row in `chat_sessions`, so `chat_sessions` then lists it and
`chat_prompt` can continue it. A nil payload or an invalid/blank id is refused
before any endpoint call; an id the endpoint does not report is refused naming
the id and records nothing; an endpoint record with an empty directory is
refused rather than substituting the home or working directory. The CLI
equivalent is `pipelines chat-adopt <session-id>` (`--json` for the full
response; otherwise a short `Adopted <id> · <directory>` line).
### Choosing the endpoint
By default chat brokers from the single `opencode serve` instance the server
spawns for itself, unchanged. To broker from the operator's own OpenCode service
instead, set the opt-in `-opencode-endpoint` server flag or the
`PIPELINES_OPENCODE_ENDPOINT` environment variable. Precedence is explicit flag,
then explicit environment, then the endpoint recorded on a previous run; with
none set the spawned default is used. The reference must be an http(s) URL with a
host and no credentials, query, fragment or path. It is validated once at
startup: the backend is detected from the service's own `/api/info` (V2) or
`/global/health` (native) contract, and a streamable `text/event-stream` event
path is required. A malformed reference, an unreachable host, a reachable
non-OpenCode service, or a healthy service with no SSE each disable chat with an
error naming the endpoint — never a silent fallback to another instance. An
endpoint that authenticates accepts an optional password through the private file
`PIPELINES_OPENCODE_ENDPOINT_PASSWORD_FILE` (a regular 0600 file; never an
inline secret), and `PIPELINES_OPENCODE_ENDPOINT_USERNAME` overrides the detected
default user. The validated choice is recorded so a restart with no flag or
environment keeps brokering from the same place; an unreachable recorded endpoint
disables chat with a clear message and no fallback. The endpoint choice is
preserved by `pipelines service enable` autostart (the variables, with the
password file as a reference).
The stored tag is exactly `operator`; the display label `Operator` is derived from
it, so there is no second tag vocabulary. Chat uses the server's one OpenCode