Skip to content

feat: emit structured detached launch acknowledgement - #1645

Merged
nextlevelshit merged 2 commits into
mainfrom
feat/structured-detached-launch
Sep 20, 2026
Merged

nextlevelshit merged 2 commits into
mainfrom
feat/structured-detached-launch

Conversation

@nextlevelshit

@nextlevelshit nextlevelshit commented Sep 19, 2026 •

Copy link
Copy Markdown
Collaborator

Wave's detached run path only printed a human acknowledgement to stderr, so structured local clients could not obtain the canonical run ID without scraping terminal output or guessing from “latest.”

When wave run --detach --output json succeeds, it now writes one JSON acknowledgement containing run_id, pipeline_name, status: "running", and detached: true. Text output is unchanged and quiet output remains silent. The acknowledgement means the child process was released; durable state must still be observed with wave status.

Validation: go test ./...; focused command and runner tests; gofmt; git diff --check. An installed build launched an isolated mock pipeline with JSON-only stdout, retrieved it by the returned run ID, and accepted a structured cancellation request.

This is the structured seam used by re-cinq/pi#19 so Pi can launch Wave locally without an API URL or WebUI server.

nextlevelshit and others added 2 commits May 20, 2026 11:39
The tmpfs overlay on $HOME hid the host GPG keyring inside the sandbox, so
git commits with commit.gpgsign failed with "can't connect to the keyboxd".
Bind ~/.gnupg rw, bind the gpg-agent socket dir (XDG_RUNTIME_DIR/gnupg),
and propagate GPG_TTY so pinentry-tty works.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@nextlevelshit
nextlevelshit merged commit c687f66 into main Sep 20, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant