CLI / Headless Execution Support for Roo Code

[p-goloborodko]

What problem does this proposed feature solve?

Currently, Roo Code requires the VS Code UI to function. This limits its usability in scenarios where a graphical interface isn't available or desirable, such as automated testing, CI/CD pipelines, server-side execution, and scheduled or triggered tasks.

Describe the proposed solution in detail

We propose adding a headless execution mode to Roo Code, enabling users to run tasks via a command-line interface (CLI) or as background services without requiring the VS Code UI.

Key functionalities:

• CLI Interface: Introduce a new CLI command that accepts arguments specifying the workflow, agent, or task to execute, along with any necessary input parameters.
• Configuration Options: Allow users to configure Roo Code's behavior in headless mode through a configuration file or command-line arguments.
• Deterministic Action Handling: Implement a mechanism to handle actions that currently require user approval in a deterministic manner. This could involve:
• Background Service Support: Enable Roo Code to run as a background service or daemon, allowing for scheduled or triggered execution of tasks.
• Output and Logging: Provide detailed output and logging capabilities to track the progress and results of headless executions.

Technical considerations or implementation details (optional)

No response

Describe alternatives considered (if any)

Using Alternative Solutions (like Aider): Other solutions like Aider exist that provide CLI interface. However, Roo Code was performing better on our tasks, so we would prefer to continue using it.
Using a Minimal VSCode Instance: This approach involves launching a minimal, potentially hidden, instance of VSCode to run the Roo Code extension, and communicating with it via roo-cli or something else. While it offers compatibility with existing Roo Code logic, it also introduces significant overhead and may require a virtual display server. This approach may not be suitable for production headless execution.

Additional Context & Mockups

No response

Proposal Checklist

• I have searched existing Issues and Discussions to ensure this proposal is not a duplicate.
• This proposal is for a specific, actionable change intended for implementation (not a general idea).
• I understand that this proposal requires review and approval before any development work begins.

Are you interested in implementing this feature if approved?

• Yes, I would like to contribute to implementing this feature.

[5hanth]

A Roo Code MCP would be better.

[daniel-lxs]

Hey @p-goloborodko, do you have any technical details about this feature you're proposing?

We would like to know if you have looked into this on a more technical level since, in my opinion, this feature might require a lot of work.

[flazouh]

Why was aider not good for you ?
Have you found other solutions?

[cte]

We currently support running Roo Code headlessly inside of a Docker container, which is the foundation of our evals system. The key package to look at is @roo-code/evals: https://github.com/RooCodeInc/Roo-Code/tree/main/packages/evals

You can also run Roo Code headlessly in the cloud (or via local conatiners), as demonstrated by this WIP PR: #4551

And finally, you can build a cli application by plugging in to the IPC server that can optionally be enabled when running Roo Code (headlessly or otherwise). Here's how you can do that: https://github.com/cte/roo-cli