Remote Dev Environments

On-demand cloud dev machines — macOS and Linux — running on the same infrastructure, stacks, and caches as Bitrise CI. Spin one up in seconds, connect from your terminal, IDE, or AI agent, then archive it and restore it later.

OverviewQuickstart

Get started

Remote Dev Environments overviewWhat RDE is, who it is for, and the different ways to use it.QuickstartInstall the CLI and start a Claude Code session in three commands.Key conceptsSessions, templates, saved inputs, stacks, and the session lifecycle.Remote Dev Environments FAQCommon questions about sessions, storage, connecting, credentials, and limits.

Ways to use RDE

Bitrise RDE CLIManage sessions and run AI coding agents from your terminal.Bitrise RDE UICreate and manage sessions, templates, and saved inputs in the browser.MCP server for AI agentsLet any AI assistant create and drive sessions over the Model Context Protocol.Connecting to a sessionReach your session over a web terminal, SSH, VNC, or VS Code Remote.

Devices

Virtual devicesiOS simulators and Android emulators on RDE, and which way to use them.Device sessionsBoot a simulator or emulator with a session and drive it yourself or with an AI agent.Device preview linksShare an app build as a link that runs it on a device in the browser, no login needed.

Configuration

TemplatesDefine reusable session configurations with setup scripts and inputs.Saved inputsStore reusable credentials and values, including secrets, for your sessions.GitHub integrationLet sessions authenticate to GitHub as you: git and the GitHub CLI work out of the box.Managing RDE accessGrant and revoke RDE access for workspace members and groups, or automate it with SCIM.