Start Here
When RemoteMux behaves unexpectedly, inspect the resolved config and current binding first:backend=e2b and backend=managed do not have dedicated preflight commands — use rmux configure --show.
Many problems come from running commands outside the directory that created the environment binding. Make sure you are in the right project directory.
Binding And Directory
No binding found for this directory
No binding found for this directory
You are in the wrong directory or have not created an environment for this project. Re-enter the directory that ran
rmux env new, or create a new environment.This directory is already bound
This directory is already bound
Use
rmux workspace attach to reconnect, rmux env status to inspect, or rmux env destroy if you want to replace the environment.AWS
rmux aws-check fails before environment creation
rmux aws-check fails before environment creation
Confirm
backend=aws is selected, AWS credentials are valid, and the region is correct. Run rmux configure --show to verify.Attach fails on AWS backend
Attach fails on AWS backend
Attach uses the AWS Session Manager plugin, bundled in RemoteMux releases. If you have the plugin elsewhere, set
RMUX_SESSION_MANAGER_PLUGIN_PATH.aws.workspaceBucket must be configured
aws.workspaceBucket must be configured
RemoteMux needs a workspace bucket for staged sync. On the BYOC default path, rerun
rmux aws-check or rmux env new to let RemoteMux auto-resolve it. Otherwise, set --workspace-bucket or aws.workspaceBucket explicitly.GCP
compute.googleapis.com is not enabled
compute.googleapis.com is not enabled
Enable the Compute Engine API in the target project, then rerun
rmux gcp-check.rmux gcp-check fails even though I am logged in
rmux gcp-check fails even though I am logged in
Verify the resolved auth mode, project, and zone match the RemoteMux config. Compare
rmux configure --show with gcloud auth list when gcp.authMode=gcloud-cli.If you use gcp.authMode=credentials-file, confirm gcp.credentialsFile or RMUX_GCP_CREDENTIALS_FILE points to a readable credential file, and re-check any gcp.impersonateServiceAccount setting.Managed
Managed commands fail against the control plane
Managed commands fail against the control plane
Check
apiBaseUrl and your auth state with rmux auth status. Hosted deployments require a valid OAuth session or scoped service token. If commands fail in an interactive terminal, rmux now offers an auth picker automatically; otherwise switch explicitly with rmux auth use oauth or rmux auth use api-key --token <api-key>.If the active source is env, unset RMUX_API_KEY. If the active source is none, select a stored auth method with rmux auth use ....Workspace bootstrap fails or times out on managed
Workspace bootstrap fails or times out on managed
Contact your RemoteMux operator — the control plane may be using a sandbox template that lacks the required dev tools.
E2B
e2b.apiKey must be configured
e2b.apiKey must be configured
Confirm
backend=e2b is selected and the API key is present. rmux configure --show should show the backend, template, timeout, and a masked key.E2B bootstrap requires apt-get or dnf
E2B bootstrap requires apt-get or dnf
RemoteMux installs
tmux, git, and python3 on first use. Choose a template with apt-get or dnf available.Sync And Workspaces
Remote code looks stale
Remote code looks stale
rmux workspace new main only seeds the project once. Use rmux env sync or git to move later changes.Claude works locally but not in the workspace
Claude works locally but not in the workspace
Run
rmux claude status from the project directory. If local auth exists but remote auth is missing, run rmux claude sync. If local auth is missing, run rmux claude login.Before You File A Bug
Capture these and include them in your report at github.com/autocomputer-ai/rmux/issues:rmux configure --showrmux auth statusrmux env statusrmux workspace ls- The relevant
rmux aws-checkorrmux gcp-checkoutput - The exact command and error message