BlueDev Container - Introduction

Introduction to BlueDev Container

BlueDev Container executes development workloads inside a devcontainer on a remote host. By moving the execution environment to dedicated host infrastructure, client machines maintain standard local workflows without bearing the computational overhead.

Core System Capabilities

Remote Workload Execution

Offloads container image builds, source code checkouts, language toolchains, and AI agent executions entirely to the remote host.

Minimal Local Dependencies

Eliminates the need for local installation of Docker Desktop, local Docker daemons, and the Docker CLI on client workstations.

Native Client Integration

Connects local development environments (VS Code, Cursor, Claude Code Desktop, and Codex) to remote containers using a local SSH proxy.

Enforced Access Control

Secures the host boundary by restricting incoming connections to a shell-less bouncer service and authenticating requests using short-lived, OIDC-signed SSH user certificates.

Deployment and Usage Flow

1

BlueDev Identity Deployment Kit

Deploy the identity service to handle OIDC authentication and issue short-lived SSH user certificates for host access. For setup/deployment details, refer to the BlueDev Identity Deployment Kit doc.

2

BlueRock Connector for VS Code and Cursor

Install and configure the editor extension to attach local VS Code or Cursor sessions to remote containers via the BlueRock Identity or local SSH proxy. For setup and usage details, refer to the BlueRock Connector for VS Code and Cursor doc.

3

BlueRock Connector for Claude and Codex IDE

Deploy the desktop application and CLI to connect standalone AI agents (Claude Code Desktop and Codex) directly to remote sandboxes. For setup and usage details, refer to the BlueRock Connector for Claude and Codex IDE doc.

Important:

The guides in this current section apply to the latest BlueRock release v26.23.1. For documentation regarding BlueRock v23.26.0, please refer to the Archive (v26.23.0) section.