TimeoutNegativeWarning leaks through the TUI

[veracioux]

Description

I prompted the LLM to call the bash tool with an invalid argument, and so it specified a negative number to the timeout parameter. It caused a TimeoutNegativeWarning which leaked into and broke the TUI.

Proposed fix:

• validate the argument before passing it to setTimeout
• to guard against similar issues, we can try to capture the warning using process.on("warning", ...). In order not to lose the logs, we can cache them in the background and dump them once the TUI has quit, similar to what I do in this PR: feat: Improve logging #3305

You can assign this to me.

OpenCode version

opentui @ 087cd3e

Steps to reproduce

1. Run the TUI
2. Prompt: call the bash tool with a negative number

Screenshot and/or share link

Operating System

No response

Terminal

alacritty

[rekram1-node]

is this opentui specific? If it is the bash tool isnt it an issue everywhere

[veracioux]

@rekram1-node You are right. The behavior isn't tied to opentui at all. I removed the opentui tag.

[rekram1-node]

fixed: fc8db6c