Enforce 30-second minimum timeout on bash commands

The model passes timeout values thinking they are seconds (e.g. 60)
but the tool reads them as milliseconds, killing nmap/curl/ping in
15-60ms before they can even connect. Now any timeout under 30s is
bumped to 30s so network commands actually have time to finish.

Author: itwizardo

rust/crates/runtime/src/bash.rs

@@ -109,7 +109,11 @@ async fn execute_bash_async(
 ) -> io::Result<BashCommandOutput> {
     let mut command = prepare_tokio_command(&input.command, &cwd, &sandbox_status, true);
 
+    // The model often passes timeout values thinking they're seconds (e.g. 60)
+    // but the parameter is in milliseconds.  Enforce a 30-second floor so
+    // network commands (nmap, curl, ping) actually have time to finish.
     let output_result = if let Some(timeout_ms) = input.timeout {
+        let timeout_ms = timeout_ms.max(30_000);
         match timeout(Duration::from_millis(timeout_ms), command.output()).await {
             Ok(result) => (result?, false),
             Err(_) => {

rust/crates/tools/src/lib.rs

@@ -5985,6 +5985,9 @@ fn execute_shell_command(
         .stderr(std::process::Stdio::piped());
 
     if let Some(timeout_ms) = timeout {
+        // Floor: 30 seconds minimum — the model often passes small values
+        // thinking the unit is seconds, but it's milliseconds.
+        let timeout_ms = timeout_ms.max(30_000);
         let mut child = process.spawn()?;
         let started = Instant::now();
         loop {