[GPT-6.1 Sol][Codex] on behalf of shivam.
Handoff from the issue-watch investigation of https://github.com/pingdotgg/t3code/issues/27811. These results cover my unpushed branch, ending at a14676f47d0f59fba32f7059b2467abdb10efc46, with production code from 547ad9bf15b0be9650bd6b00ce9313dc94dd3774.
- Reproduced on corex's Linux web client against baseline
7f005d4d8d5b6226fad707b0e5f679fa391bf46f, using real glab 1.126.0 with an isolated config and local synthetic GitLab API. Two hosts signed in and a third returned 401. Plainglab auth statusprinted only the default host;--allprinted all three and exited 1. Settings showed only the default-account summary. - My display-list fix showed both signed-in hosts and the failed host's 401 after rescan and expanding GitLab. The default account stayed unchanged. A real glab 1.78.0 probe also returned all three through plain status when
--allwas rejected. - Focused tests failed first on the missing host list. The source-control/server suites passed 223 tests across 18 files. After the test-only follow-up, the two GitLab files passed 18 tests, and
vp run check:changedpassed format, lint, knip, typecheck across 35 packages, tests and React compiler checks. - One useful limit: glab buffers status output until every host finishes, with a 30-second request deadline per host. An unreachable host made a real
--allrun take about 53 seconds before any output. A five-second probe therefore cannot retain partial host results. My branch preserves the default-host fallback and has a focused timeout case.
macOS verification had not started; I cancelled its queued job on takeover. No desktop or mobile result is claimed, and I have not tested this PR. Local test servers and the browser are stopped. Nothing was pushed.
Corex web baseline, default-account summary only:
Corex web on my display-list fix, two signed-in hosts and one 401:
Corex web recording of rescan and expanding the host list:
https://github.com/user-attachments/assets/1ea19db7-5739-4af1-95e0-9a05d3985b7b