Repository navigation
content: Launch post — Enroll PIG Hosts Without a Browser - #1104
frances720 wants to merge 1 commit into
Conversation
Generated by launch-post skill. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AVCfFeMWZLiXT7hWrWyvFs
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Promptless inbound docs review: I checked correctness against Enroll your hosts (merged in #1056) and the source PRs, plus style and frontmatter against the other product-updates posts.
Verdict: comment. Accurate: the command (python3 "$PIG_PLUGIN_ROOT/runtime/promptless-host-runtime" enroll --host codex --device), the ~35-second poll, setup_pending resume, the 15-minute expiry, the --host values, and the prerequisites in "How to use it". Frontmatter and components match the existing launch posts.
- Release state (blocking for publish). Both source PRs behind
--deviceare still open and undeployed: the client flag in Promptless/pig-toolchain#98 and the backenddevice-sessionsendpoint in Promptless/promptless#5250. #5250 also has a mandatory rollout gate (Service change, backend deploy, then enabling the client). Until both merge and ship in a releasedpigplugin,enroll --devicewon't work for readers, so this post shouldn't merge before then. When it does go out, updatesubtitle/dateto the real publish date; right now they say September 28. - Duplicate launch post. #1105 (
browserless-host-enrollment.mdx) announces the same--devicefeature and is open at the same time. Only one should merge, so a maintainer should pick one and close the other. Of the two, this one is more accurate: it uses the real bundled-runtime invocation and states the prerequisites. - One inaccuracy about how standard enrollment works (inline).
|
|
||
| ## The problem | ||
|
|
||
| Standard enrollment opens a browser tab at `127.0.0.1` on the host to complete the authorization callback. On a developer's workstation, that's invisible: the tab opens, they approve, enrollment finishes. On a headless server, there is no browser to open. Teams that wanted trace collection on remote or cloud-hosted agents were stuck, either limiting PIG to local workstations or working around the constraint with X forwarding or manual credential handling. |
There was a problem hiding this comment.
Inaccurate: standard enrollment doesn't open a browser tab at 127.0.0.1. The browser opens the approval page at app.gopromptless.ai/instruction-hub/enroll, and the runtime listens on a local 127.0.0.1 callback while approval completes (see Enroll your hosts, step 3). Suggested wording:
Standard enrollment opens the Promptless approval page in a browser on the host and completes through a local
127.0.0.1callback.
Also, "X forwarding or manual credential handling" isn't backed by any source, and the guide says not to copy host credentials between machines. I'd cut that clause or replace it with "port-forwarding the loopback callback".
|
Closing: the automated content pipeline is being turned off and these generated drafts will not be merged. The branch is left in place in case anything is worth salvaging. |
Feature
PIG host enrollment now works on headless servers and SSH-only machines via the
--deviceflag. The host prints an approval URL; a developer opens it on any device with a browser and approves. No local browser, inbound port, or loopback callback required on the host.Entries considered this run
Window: 2026-09-28 → 2026-10-05.
enroll --device, open the printed approval link on another device and approve the host theresource-pr:123to find suggestions triggered by a specific source PR or MR2 commit(s) in window. 2 entries considered, 1 qualified.
Covered entry (full text)
Source: commit f595e04.
PR(s) researched
File
src/content/blog/product-updates/headless-host-enrollment.mdxAI-generated draft — needs human review before publishing.
Generated by Claude Code