[Bug]: Cloud Roomote Sandbox Resources

[fdev23408]

Preflight

• I searched existing issues and docs before opening this.
• I removed secrets, tokens, private keys, customer data, and private repository details from logs and screenshots.
• This report describes observed behavior, not a speculative AI-generated rewrite request.

Summary

The cloud Roomote sandboxes may be under provisioned for compute. It struggles to maintain speed of setup and the Roomote agent has reported the sandbox to be stuck. It seems to do fine with basic websites with a database. It gets stuck when the repo contains a more complex codebase. The ability to provision more resources is available in the self-hosted version of Roomote so it is a non-issue there. It may be a little tight in the cloud version for real work on more complex stuff or larger repos.

A separate issue or maybe related, some better guidance is also needed in the Roomote docs on environment setup and configuration. We have tried multiple models (openAI Sol,Luna,Terra, Qwen) and multiple methods like referencing an agents.md file and detailes about the codebase (apache, php 8.x, MCV/HMVC, etc) in the prompt. We have experienced several environment setup failures in both cloud Roomote and self-hosted(with increased resources).

Affected surface

Setup, deployment, or upgrade

Steps to reproduce

Take a more complex repo or codebase with multiple sub-containers or multiple DBs or repos and attempt to setup an environment with the Roomote agent. You might try a fork of Roomote itself.

Expected behavior

If not already baked in, environment resources could potentially be estimated before provisioned so they are elastic to some reasonable limits before sandbox is provisioned. More documentation is needed for environment setup in roomote docs to accomodate more complex codebases and repos. A how to with some examples would be helpful.

Actual behavior

Environement setup and sandbox slows to a halt and becomes stuck causing multiple attemtps by the user to remove and recreate the environment without success. Docs lack clear directions and walkthrough on environment setup. In some cases the Roomote agent will state that the envionment is ready when it clearly fails.

Roomote version

main-82eebfdc

Installation method

Source checkout / development

Deployment context

Cloud Roomote

Diagnostics output

Instance

Generated at: 2026-08-02T08:53:14.961Z
Roomote version: main-82eebfdc
Git commit: Unknown
Docker image tag: main-82eebfdc
Deployment mode: production

Runtime

Node version: v24.13.1
pnpm version: Unknown
OS: linux
Architecture: x64
Containerized: Unknown
Timezone: UTC

Services

Web reachable: Yes
API reachable: No
Controller heartbeat: Yes
Worker heartbeat: Yes
Preview proxy reachable: No
Database reachable: Yes
Redis reachable: Yes
Object storage reachable: Yes

Database

Provider: PostgreSQL
Migration status: Applied
Current migration: 34becbf8d22809969520807e513b6fa22e6c27ce979db50504e24ff86bcbb3bf
Pending migrations: Unknown
Database time: 2026-08-02 08:53:14.962459+00

Compute

Compute provider: roomote
Sandbox provider: roomote
Snapshot support: Unknown
Artifact storage writable: Yes

Integrations

Communications providers configured: slack
Source control providers enabled: gitea, github
MCP servers configured: 0

Configuration Warnings

Missing required env vars: None detected
Suspicious public URL/callback mismatch: Unknown
Webhook secret configured: No
Encryption key configured: Yes
Default credentials detected: Yes

Logs, screenshots, task IDs, or job IDs

Additional context

No response

[roomote-community]

I'd like to help with this issue, but I need some clarification to separate sandbox resource exhaustion from environment configuration and readiness-reporting problems. The current code uses different fixed memory tiers for ordinary and nested-Docker tasks, and setup records command outcomes and performs a follow-up readiness check, so a concrete failed run will help identify which path is breaking.

Could you please provide:

• One or more Roomote task links or task IDs for failed cloud environment-setup attempts, including one that was reported ready despite failing, if available.
• For one representative run, the approximate time it stopped making progress, the last setup command or log line shown, and any exit code or message such as 137, out-of-memory, disk-full, timeout, or container health-check failure. Sanitized excerpts from .roomote/setup-status.json and the matching .roomote/setup-logs/ file would be especially useful.
• A public reproduction repository, or a sanitized outline of the environment: repository count and approximate sizes, Docker Compose/Dockerfile usage, number of containers and databases, and the setup commands involved.
• For a comparable self-hosted failure, the CPU/memory allocation and whether it failed at the same command. This will show whether increased capacity changes the result or whether both cases share a setup/configuration cause.
• Whether the diagnostics showing the API and preview proxy as unreachable were captured during the affected setup attempt, and whether the Roomote dashboard itself remained usable at that time.

Please tag @roomote in your response with the details, and I'll use them to produce a concrete implementation plan without guessing at the cause.

[fdev23408]

Here are some task IDs as requested:
/task/26urcz2804eg6
/task/3pzurmdz6qj1d
/task/0c851chae93hs
/task/1vtyyp0m4gxs0
All failed and reported ready. Previews have never worked in all attempts. Including the fix previews with agent tasks. The self hosted failures were on different repos which are private. The issue may be more enviroment setup and less about resources; however, the resource limit in cloud hypothesis comes from a slower environment setup attempt on Cloud Roomote vs self-hosted. You could try to setup an environment for Roomote itself or another more complex repo and see what you run into. I have yet to succeed. The basic website repos with a single DB work great. It is the more complex stuff that is failing.

[roomote-community]

I saw the mention, but I need your GitHub account linked to Roomote before issue and PR comments can start work here. Link it from Settings -> Linked Accounts and then mention me again.