Validate providers and retain complete run debugging context

This commit is contained in:
2026-10-09 23:21:01 +01:00
parent f3d829bea5
commit 08b8647d5b
51 changed files with 1036 additions and 159 deletions
+40 -5
View File
@@ -23,16 +23,23 @@ changing databases, login, or OpenCode configuration files.
Docker mode detects the computer's LAN IPv4 address and timezone automatically,
configures `http://LAN_IP:8090`, and binds both Docker services to `0.0.0.0` without asking
for networking settings (timezone falls back to UTC). On reinstall it updates only
the bind settings to `0.0.0.0` and retains existing URLs/timezone/ports/credentials. It bootstraps
the bind settings to `0.0.0.0`, refreshes the detected host LAN IP for Status,
and retains existing URLs/timezone/ports/credentials. It bootstraps
the publishing/phone accounts and publishing token, builds the server, installs
the skill inside the container, and opens **container OpenCode provider login**
on first setup. Choose any supported provider; signup is handled by that provider.
Provider credentials remain in the `opencode-home` volume. Reinstalls skip login
after completed setup; `./install.sh --relogin` opens it again without
deleting accounts. The installer then starts/recreates the Compose services,
deleting accounts. Setup asks which connected provider/model to validate, then
requires a real, small **tool-free model response** before marking setup complete
(provider charges may apply). `--model PROVIDER/MODEL` selects it explicitly;
reinstall retests the saved selection. New drafts/templates inherit this selection;
published definitions and retry versions stay unchanged. Failed checks print
bounded, credential-redacted evidence and retain their OpenCode session.
The installer then starts/recreates the Compose services,
checks ntfy health through Pipelines, and sends an authenticated test notification.
It does not register an OS service, delete volumes, or seed pipeline definitions.
Phone reception/model inference are not verified by installation.
Phone reception is not verified by installation.
For fresh configuration you can supply `--ntfy-url https://ntfy.example.com
--bind-address 127.0.0.1 --timezone Europe/London --port 8081` directly to `./install.sh`.
@@ -45,8 +52,36 @@ The Docker Pipelines API is unauthenticated: keep its port on a trusted network
and do not forward it to the Internet. For a manual loopback-only deployment,
set `PIPELINES_BIND_ADDRESS=127.0.0.1` after installation and use Compose directly.
Ctrl+C cancels cleanly without deleting configuration, credentials or volumes.
Install native mode as well if you want host CLI/TUI binaries; Docker mode installs
the server and CLI in its image. See [Docker setup](docker.md).
If Go is available, Docker setup also updates standard host CLI/TUI binaries and
the skill. Restart an already-running TUI to load the changes. Without Go, the
installer explicitly warns that the host client was not updated; use native
installation when Go is available. See [Docker setup](docker.md).
## Failure evidence and confirmations
TUI run/retry/cancel requests cannot be sent before their confirmation modal.
Draft creation/editing and opening a debugging session also require approval.
CLI mutations prompt with a default of No; `--yes` is explicit noninteractive
approval. The standalone TUI always keeps its modals, including with `-yes`.
`pipelines debug RUN_ID --no-open` retrieves the retained run plus read-only
OpenCode session evidence from the **server**, not the client's unrelated service.
Debug includes the exact pinned pipeline definition and full run snapshot directly.
Large context packets are retained in a private client cache file which OpenCode
is instructed to read, rather than discarding evidence or exceeding argument limits.
New failed operations retain operation, provider/model, executable, directory,
timing, exit/HTTP status and bounded stdout/stderr under `opencode_failures` in
the step transcript. Credentials are redacted, but project/provider messages may
still contain private context: review before sharing. Older failures cannot gain
discarded subprocess output retroactively; Debug attempts retained session reads.
To validate a model on the execution computer, run:
```sh
pipelines provider-check --model PROVIDER/MODEL
# Docker credentials are separate from host credentials:
docker compose exec pipelines pipelines provider-check --model PROVIDER/MODEL
```
For a private repository, use your normal Git credentials and `GOPRIVATE`: