> For the complete documentation index, see [llms.txt](https://docs.bluerock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluerock.io/bluedev-container/bluedev-container-introduction.md).

# 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

{% stepper %}
{% step %}

#### 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](/bluedev-container/bluedev-identity-deployment-kit.md).
{% endstep %}

{% step %}

#### 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](/bluedev-container/bluerock-connector-for-vs-code.md) and [Cursor](/bluedev-container/bluerock-connector-for-cursor-ide.md) doc.
{% endstep %}

{% step %}

#### BlueRock Bridge Connector

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 Bridge Connector](/bluedev-container/bluerock-connector-for-claude-and-codex-ide.md) doc.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**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)](/bluedev-container/archive-v26.23.0.md) section.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bluerock.io/bluedev-container/bluedev-container-introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.