Manage Bitrise Remote Dev Environments (sessions, templates, …)
Manage Bitrise Remote Dev Environments — sessions, templates, saved inputs, and the machine catalog (stacks, machine types).
Workspace resolution (highest to lowest precedence): --workspace ID flag on the rde command BITRISE_WORKSPACE_ID environment variable default_workspace_id saved with 'bitrise-cli config set' auto-detect when none of the above is set and you have exactly one workspace
Saved inputs are user-scoped — they do not require --workspace.
bitrise-cli rde session list --workspace WORKSPACE_ID
bitrise-cli rde session list --output json
bitrise-cli rde template list
-h, --help help for rde
--workspace string workspace ID (or set BITRISE_WORKSPACE_ID or default_workspace_id; auto-detected if you have exactly one workspace)
--no-color disable ANSI colors (NO_COLOR env is also honored)
-o, --output string output format: human|json (default "human")
-q, --quiet suppress non-error diagnostic messages
--theme string color theme: auto|dark|light|none (default "auto"; overrides terminal background detection)
- bitrise-cli - Bitrise platform CLI
- bitrise-cli rde claude - Create an RDE session and attach to Claude Code
- bitrise-cli rde machine-type - List machine types compatible with a given stack
- bitrise-cli rde saved-input - Manage saved inputs (reusable credentials/values)
- bitrise-cli rde session - Create, list, inspect, and manage RDE sessions
- bitrise-cli rde stack - List machine stacks available to the workspace
- bitrise-cli rde template - List and inspect RDE templates
- bitrise-cli rde usage - Show the workspace's active session and resource usage