166 Commits. 1 Month.
The Cloud Just Got Real. ☁️
Roo Code Cloud: December 2025
While the world was wrapping gifts, we were wrapping infrastructure.
In December 2025, the Roo Code team pushed 166 commits and added 88,000+ lines of code to Roo Code Cloud. This was not just maintenance. It expanded where agents can run, what they can integrate with, and what kind of environments they can depend on.
We pushed on three concrete capabilities: deeper workflow integration (Linear), a second compute vendor (Vercel Sandbox), and on-demand services (so the agent environment matches your app).
Here is what we shipped to shrink the “works on my machine” gap.
1) Linear integration: stop copy-pasting tickets
(Landed Dec 28; PR #1945, #2000)
The struggle: Your team’s work lives in Linear, but your code lives somewhere else. You become the human router (copy issue description, paste into prompt, recopy updates). It is pure toil.
The fix: We built a full Linear integration. It connects via OAuth, carries issue context into the agent run, and syncs back useful artifacts (status, actions, plans).
So you can: Start work from a Linear issue without rebuilding context by hand, and track progress where the team already lives.
2) Vercel Sandbox: cloud tasks you can see
(Dec 19–23; PR #1937, #1943)
The struggle: Remote compute is great until it is opaque. If you cannot open what the agent is running, you either trust blindly or switch back to local just to see the localhost port.
The fix: We added Vercel Sandbox execution alongside Fly.io and surfaced task preview links. You can open what the job is serving while it runs.
So you can: Stop guessing. Open the preview, watch the app change, and treat cloud tasks like something you can interact with.
3) Services Manager: databases on demand
(Dec 23; PR #1951, #1956)
The struggle: A blank container is not a development environment. “It compiles” is not the same as “it runs.” If your feature needs Postgres but the agent has no database, the code fails the second it hits CI.
The fix: We shipped the Services Manager. You can now configure roomotes.yml to request ephemeral services like Redis 7, Postgres 17, or ClickHouse.
So you can: Give the agent a real environment to run migrations and integration checks. Catch the “it fails when it touches the database” class of bugs earlier.
Tradeoff: spinning up real services can add time to a run. That is the cost of catching the right failures early.
4) The unified Fixer agent
(Dec 10–12; PR #1872, #1894)
The struggle: Separate fixers with different behaviors create a new kind of work. You end up learning which bot is safe to trust today.
The fix: We unified the PR Fixer and Issue Fixer into a single Fixer agent and enforced approval requirements before implementing issue fixes.
So you can: Stop guessing. Whether it starts from an issue, a PR comment, or a message, the control boundary stays predictable.
The theme: Connection
December was about connecting the parts that usually break a workflow.
Workflow connection: Linear issues to agent sessions.
Compute connection: Fly.io plus Vercel Sandbox as places work can run.
Data connection: Services that match what your app expects.
Roo Code Cloud is not a place to run scripts. It is a place where agents can do real product work, with visible execution and clear control boundaries.
If you want a quick way to try the new flow, start from a Linear issue, keep approvals on, and open the task preview while it runs.
Let’s ship.
Want to try Roo Code Cloud? Start here.