Uh oh!
There was an error while loading. Please reload this page.
feat(cli): clearer remote errors and a live status line - #117
Merged
Conversation
Transport failures now say whether DNS, the connection, TLS, or a timeout failed, name the host, and state the recovery step. Server 5xx fallbacks say to retry in a minute. Final rate limits state the Retry-After wait. Network commands show a TTY-only status line on stderr with elapsed time. It starts after output-mode detection, erases before any command output, and stays silent for Agents, CI, pipes, and --json.
harlan-zw
commented
Aug 21, 2026
CollaboratorAuthor
Checked by hand, since CI cannot cover it:
|
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent-authored (opencode).
Description
Every network failure printed the same string:
Wifi off, DNS dead, TLS rejected, timed out: identical output, no next step. Same story server side. A 5xx got you
the remote service returned HTTP 500and a spent 429 said nothing about how long to wait.Transport errors now name the cause and the recovery:
A 5xx says to retry in a minute. A final 429 states the wait, read from
Retry-Afterwhether the server sent a problem body or only the header.The network commands also sat silent while they worked. On a human terminal they now show
Searching… 3son stderr, erased before any real output lands. Agents, CI, pipes, and--jsonsee nothing.Wiring that up surfaced an old deadlock:
mainheld aStderrLockfor its whole body, so the status thread writing through theStderrhandle blocked forever. It passes the unguarded handle now.Legacy Windows conhost is untested; the erase sequence assumes Windows Terminal or newer.