Missing retry if /btw command encounters an error #55487

Activity

1. opencode-agent commented on Oct 14, 2026

   

   opencode-agentBot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for reporting this! If I understand it right, you'd like /btw to recover from transient server or network errors instead of failing straight away.

   From the current code:

   • In the TUI, a failed /btw request only shows an error toast. There's no retry option, and you have to type the question again.
   • On the server, /btw sends a single request to the model. It doesn't seem to get the automatic retry on transient errors that normal session messages get.
   • The desktop/web app's /btw panel already has a Retry button when a request fails.

   I've marked this as a feature request so maintainers can consider it. Until then, re-running /btw with the same question is the only workaround in the TUI.

   Related issues, in case they're useful:

   • [FEATURE]: a /btw answer is unrecoverable once its dialog closes #50879: a /btw answer can't be recovered once its dialog is closed
   • feat(tui): continue btw answers in a fork #50391: continue /btw answers in a fork
   • Concurrent sessions retry a failing provider independently — no shared backoff or circuit breaker (2.0) #55075: provider retry/backoff behaviour across sessions

   If you're seeing this somewhere other than the v2 TUI, please reply with your opencode --version and where you're using it.
2. rekram1-node

   closed this as completedin #56497on Oct 17, 2026