Skip to main content

Docs changelog

Subscribe to RSS

This page tracks documentation updates: new guides, updated procedures, and changes reflecting new or updated Bitrise features.

2026 Q4Click to copy link​

No updates match the current filters in this quarter.

2026 Q3Click to copy link​

Warm pools for Remote Dev EnvironmentsClick to copy link​

You can now keep pre-booted Remote Dev Environment sessions ready in a warm pool, so new sessions and device preview links open in seconds. Create pools in the UI, the CLI, with an AI agent, or through the API. See Warm pools.

Sessions opened from a device preview link now always belong to the workspace, whichever credential created the link. You find them under Workspace sessions, not in your personal session list. See Device preview links.

Remote Dev Environments adds virtual devicesClick to copy link​

You can now use an iOS simulator or Android emulator on Remote Dev Environments, either through an interactive device session or a shareable device preview link. See Virtual devices.

Remote Dev Environments is generally availableClick to copy link​

Remote Dev Environments has left beta. The beta notice has been removed from the RDE documentation, and the overview now points to self-serve sign-up alongside the sales route. The RDE API is still marked experimental: endpoints and payloads can change in backwards-incompatible ways. See Remote Dev Environments overview.

Track Remote Dev Environments usage across API, CLI, MCP, and UIClick to copy link​

You can now check RDE workspace usage through the REST API, the rde usage CLI command, the MCP server, or the UI. See Remote Dev Environments API.

Remote Dev Environments FAQ, and a corrected session retention modelClick to copy link​

New Remote Dev Environments FAQ answers the most common questions about sessions, storage, connecting, credentials, AI coding agents, and limits.

The session retention documentation was also corrected. Terminated sessions are not cleaned up after a fixed period: a session's persistent disk is kept until you delete it, or until the stack it was created from is removed under the stack deprecation and removal policy. Key concepts now also explains that a session stays permanently tied to the stack it was created from and can't be moved to a different one.

Manage Remote Dev Environments access from CollaborationClick to copy link​

RDE is now a standalone product in workspace collaboration: grant or revoke the RDE User role for members and groups from the Collaboration page, or assign it through SCIM with rde:rde_admin. See Managing RDE access.

RDE CLI docs refreshed to match current commandsClick to copy link​

The RDE CLI reference now covers stack-based session creation, running commands in a session with session exec, VNC tunneling, workspace selection, and the reconnect behavior of rde claude. See Bitrise RDE CLI.

Building a Slack-native coding agentClick to copy link​

A new recipe walks through a reference architecture for a Slack-native coding agent: a locked-down orchestrator that delegates coding work to disposable Remote Dev Environments, plus an open source reference implementation you can try. See Building a Slack-native coding agent.

2026 Q2Click to copy link​

RDE API reference now available in-siteClick to copy link​

The Remote Dev Environments REST API reference is now part of docs.bitrise.io as a native interactive explorer, covering 42 endpoints across user, workspace, sessions, templates, and saved inputs. See RDE API reference.

Remote Dev Environments docs now availableClick to copy link​

Documentation for Bitrise Remote Dev Environments (RDE) is now available, covering key concepts, a quickstart, configuration options (templates, saved inputs), and the available interfaces: CLI, MCP server, UI, and VS Code plugin. See Remote Dev Environments.

2026 Q1Click to copy link​

No updates match the current filters in this quarter.

<head> <meta name="robots" content="noindex, follow" /> </head>