[ENHANCEMENT] Allow continuing while running a command on time/specific commands

[LousyBook94]

Problem (one or two sentences)

The long running comamnds (started a server, or installing huge dependiencies) would cause roo to hang while its running, if left like that with no user input it would be running like that (servers) for when the users back without continuing it

Context (who is affected and when)

People who leave Roo unattended to complete a task by itself

Desired behavior (conceptual, not technical)

A command max wait time in settings would be nice with a default of about 30 seconds AND a auto skipped commands list which run but will let roo do other tasks while that, default for that would be (* install, * run dev and etc)
BUT IF THATS ALL ROO HAS TO DO, roo can use a tool to wait until the command is done before moving on

Constraints / preferences (optional)

Adding a new area in the command settings

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I'm exploring a potential fix for handling long-running commands more gracefully. I'll work on adding configurable timeout settings and background command patterns as suggested.

[roomote]

I've opened PR #8461 with my attempt at addressing this issue. The implementation adds:

Features Implemented

• Command Max Wait Time: Configurable timeout (default 30 seconds) after which Roo continues with other tasks
• Auto-Skipped Commands: List of command patterns that automatically run in background (supports wildcards)

Technical Details

• Added new settings to global-settings schema
• Updated TerminalProcess with timeout logic and background command detection
• Added UI controls in Terminal Settings panel
• Comprehensive test coverage for the new functionality

Current Status

The PR has some CI failures related to translations and unit tests that may need attention. The core functionality is working as evidenced by passing integration tests.

PR Link: #8461

Feedback and guidance are welcome!

[LousyBook94]

wait we also need to show the remaining time for the command probanbly on the "Proceed while running" button, and then we should have a button to cancel that auto skip timer

[hannesrudolph]

In response to your contribution, I want to note that there are currently settings to set the max command execution timeout within the VS Code level settings. We are looking towards a more interactive experience between Roo Code and the Terminal for our next iteration. As such, we are closing this issue.