[FEATURE]: Fast failure on network errors and concise error output #39771

Activity

1. github-actions

   assigned

   kitlangton

   on Jul 30, 2026
2. github-actions commented on Jul 30, 2026

   

   github-actionsBot

   on Jul 30, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • No issue template was used. Please resubmit using one of the three required templates: Bug Report, Feature Request (title must start with [FEATURE]:), or Question. Bug reports require a Description field with reproduction steps and system/environment information. Feature requests require a verification checkbox and a description of the problem or need.
   • This issue combines two separate concerns (network timeout behavior and error output verbosity) — consider splitting them into separate issues using the appropriate templates.

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Desktop/Server: Auto-updater and models.dev fetch lack network resilience (excessive errors in restricted networks) #35090: Desktop/Server network resilience in restricted networks (also mentions China, no fallback for blocked connections, similar suggestion of pre-flight network check)
   • Sessions fail on transient network errors instead of retrying #30611: Sessions fail on transient network errors instead of retrying (transport-level failures like ETIMEDOUT, ENOTFOUND, flaky connections)

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jul 30, 2026
4. openchat-ai

   changed the title [-]No fast failure on network errors, verbose output wastes tokens[/-] [+][FEATURE]: Fast failure on network errors and concise error output[/+] on Jul 31, 2026
5. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jul 31, 2026
6. github-actions commented on Jul 31, 2026

   

   github-actionsBot

   on Jul 31, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for updating the issue! It now follows the contributing guidelines and looks good. We appreciate the clear problem description and proposed solution.
7. openchat-ai commented on Jul 31, 2026

   

   openchat-ai

   on Jul 31, 2026

   Author

   More actions

   I reviewed the potential duplicates mentioned by the bot.

   #35090 (server-side network resilience) — That issue is about making the Desktop/Server architecture survive restricted networks. This issue is about client-side UX: the shell tool hanging for 60-120s before failing. Different layer, different fix.

   #30611 (automatic retry on transient errors) — That issue proposes retrying automatically when network errors occur. This one proposes the opposite: fast failure when the network is clearly unreachable. The two are complementary — do a quick pre-flight check first (e.g. \curl --connect-timeout 3); if the probe fails, fast-fail immediately; if the probe succeeds but the actual request fails, then retry. But right now there is no probe, just a blind 60-120s wait.

   I don't think either is a true duplicate.
8. github-actions commented on Sep 29, 2026

   

   github-actionsBot

   on Sep 29, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
9. github-actions

   closed this as not plannedon Sep 29, 2026