Troubleshooting

The CLI cannot reach Adria

Confirm you are using the CLI and connection instructions provided for your workspace. Early distributions need the workspace API origin configured as instructed by your Adria contact.

If the error refers to 127.0.0.1 or localhost on your computer, the CLI is targeting a local development service. Use your workspace's connection instructions before running cube login.

GitHub authorization is missing

Run cube auth to check status, then cube auth github to connect or renew authorization. Confirm your GitHub account has access to the target repository.

For a missing dashboard repository, check the GitHub App installation and allow time for indexing.

A branch name is ambiguous

Run the command from the intended repository, or use the Session UUID from cube sessions. Adria uses your repository and Git remotes to resolve branches. See repository selection.

Startup is taking longer than expected

cube start feature/payments --diagnostics --timeout 30m

The default readiness timeout is 20 minutes. A timeout or Ctrl+C ends the local wait; it does not necessarily delete the requested Session. Check cube sessions before starting another one.

My agent configuration is not available

Run cube config status. A queued import is still local; an accepted import may still be preparing. Wait for ready.

Import again after local changes. Existing Sessions pick up changed imports on subsequent agent launches. MCP tools may need their own dependencies or login.

My environment files are missing or out of date

From your local repository, run cube env list to check the saved paths and key names. Import the files if needed, then use cube env apply <session> for a running computer. Restart your app to load the values.

If Adria reports a conflict, it has preserved edits made inside the sandbox. Review them before applying with --force. See Environment variables.

A preview will not connect

Check that the Session is ready and the server is running on the port you are forwarding. cube open and cube forward do not resume a paused VM.

If the app runs in Docker, publish its port to the VM. Use the local address printed by the forwarding command, especially when your requested port is occupied.

Desktop commands report desktop_not_installed

Desktop capabilities require an image with computer-use support. A CLI update alone does not add them to an existing sandbox. Use a supported image for your workspace; see computer use.

Agent status says unknown

Status is based on observed agent activity and requires capture support in the image. Capture gaps, older images, or an unrecognized agent interface can leave the state unknown. Inspect the actual terminal before assuming the task has stopped.

A Notion update conflicts

The page changed after the proposal was created. Review its current content and the proposal before retrying. See reviewing agent work.