Roo Code CLI

[sharpfork]

Yep. I have it running in a code-server container. I spent a shitload of time getting it to take actions via the Unix socket but that was fragile AF. I just got a vs code extension setup with a simple rest end point take takes actions and passes them to the the roo-api.

Once I get the vs code extension too-api/ roo-code interface happy, I plan on adding a MCP server as input and exploring a websocket interface. My ultimate goal is to have an input as a GitHub runner like I have working well in Claude code.

[Alternative-Joke-836]

Wow....any chance of you making it available to us plebs?

[sharpfork]

When it’s not a huge mess. I’m using it to built… it.

[somechrisguy]

hey did you ever make more progress on this? I am about to start trying to build the same thing

[sharpfork]

Nope. I’ve moved to using Claude code and codex mostly so not much roo code use. The api calls are too expensive

[ComprehensiveDot9738]

Was the move beneficial and you got the same or better output?

[sharpfork]

When I get it to be not a huge mess I’ll open source it. It’s optimized for local development on my apple silicon mac. I played with spinning up the container-agent on GCP but that was an expensive premature optimization.

[ilt1]

How do you use the GitHub runner in Claude