Commit: eb14ddb79924a6cbcb6c26d1b97c9816c9732c55 Environment: Linux, Node CLI independently bundled with vp run build:bundle; isolated new T3 home; Connect test stage; browser-authorized test account; no relay client installed. Capture date: 2026-11-14 UTC. Privacy: account identity and local home paths redacted; command output otherwise preserved. 1. Publish-only link after browser authorization $ t3 connect link --publish-only --headless --base-dir T3 Connect ✓ Authorized as Next Start T3 to publish agent activity (no managed tunnel). 2. Before server startup $ t3 connect status --base-dir T3 Connect Exposure: enabled Authorization: stored credential Environment link: pending server startup Relay: not provisioned Publish agent activity: enabled Relay client: not installed Next: Start T3 to provision the environment link and launch its managed tunnel. 3. Start real built server $ t3 serve --host 127.0.0.1 --port --base-dir [00:03:53.940] INFO (#610): T3 Connect desired link reconciled on startup [00:03:54.115] INFO (#963): agent activity publishing enabled after link reconciliation 4. Running server: t3 status --json $ t3 status --json --base-dir { "service": { "supported": true, "installed": true, "installedVersion": null, "otherBaseDir": "" }, "connect": { "enabled": false, "revoked": false }, "lan": { "enabled": false, "inheritedDefault": false, "hostOverride": null } } 5. Running server: t3 connect status $ t3 connect status --base-dir T3 Connect Exposure: enabled Authorization: stored credential Environment link: provisioned Relay: https://relay-factory.t3.codes Publish agent activity: enabled Relay client: not installed 6. Running server: t3 connect status --json $ t3 connect status --json --base-dir { "desired": true, "authenticated": true, "linked": true, "revoked": false, "cloudUserId": "", "relayUrl": "https://relay-factory.t3.codes", "publishAgentActivity": true, "relayClient": { "status": "missing", "version": "2026.10.4" }, "linkMode": "publish_only", "reachability": null }