Problem (one or two sentences)

When running a long-lived or daemon process (such as a Spring Boot application) via the terminal in Roo-Code, the UI blocks and waits indefinitely for the process to exit. Roo-Code treats these service-type processes as if they were interactive jobs that should eventually complete, so the next step is never triggered unless the user manually intervenes. It's unclear whether this is a bug or a design choice, but more intelligent handling would be beneficial.

Context (who is affected and when)

This affects any user who tries to run a service or daemon in the terminal using Roo-Code, such as starting a web server or application backend. It's particularly common for Java/Spring Boot projects, where 'mvn spring-boot:run' or 'java -jar app.jar' starts a process that intentionally does not exit.

Reproduction steps

1. Create a simple Spring Boot project with an HTTP endpoint.
2. In Roo-Code, use the terminal or build/run command to start the project (e.g., 'mvn spring-boot:run' or 'java -jar app.jar').
3. Observe that the process starts and logs output, but Roo-Code continues to wait as if the task is not finished.
4. The next action is blocked until the user manually stops the process or performs the next step.

Expected result

Roo-Code should detect when a process is a long-running daemon/service and not block the UI or workflow indefinitely. Ideally, it should offer the user a way to continue or fork the process into the background, so that subsequent steps can proceed without manual intervention. Even if this is a deliberate design decision (i.e., Roo-Code intentionally chooses to be "non-managed" for such processes), a smarter handling or an option to manage these cases would greatly improve the user experience.

Actual result

The Roo-Code UI remains blocked, waiting for the process to exit, even though the service is running normally in the background. User must manually stop or force the next step.

Variations tried (optional)

Tried with different types of service processes (Spring Boot, Node.js express server, Python Flask) and observed similar blocking behavior.

App Version

3.26.2

API Provider (optional)

OpenAI

Model Used (optional)

Qwen3-Coder

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)