> 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/archive-v26.23.0/bluerock-bridge-connector-26.23.0.md).

# BlueRock Bridge Connector (26.23.0)

{% hint style="warning" %}
**Important:**

This guide for BlueRock Bridge Connector is for version **26.23.0** only. For environments running platform version **26.23.1**, refer to the [**BlueRock Bridge Connector (26.23.1** **)** documentation](/bluedev-container/bluerock-connector-for-claude-and-codex-ide.md) for the updated installation steps.
{% endhint %}

BlueRock Bridge ships the Cobalt application, which enables a remote coding workspace from Claude Desktop IDE by launching and managing `bluedev containers` onto the BlueRock Host VM and supports SSH logging to the remote `bluedev container` using SSO or SSH key-based authentication.

### Pre-requisites

* [Claude Code IDE](https://claude.com/product/claude-code)
* BlueRock Bridge app `Cobalt` (Contact [BlueRock support](https://www.bluerock.io/contact) to get the Cobalt app)
  * For Windows: `BlueRock_Cobalt_win64.exe` 
  * For macOS: `BlueRock_Cobalt_macOS.app.zip`

### Installation (Windows)

Locate Cobalt's `BlueRock_Cobalt_win64.exe` application and double-click to run it. 

{% hint style="info" icon="notes-sticky" %}
**Note:**

Windows will display a standard publisher notification warning message because the application is not from Microsoft. Proceed through the prompt to install and run the application.
{% endhint %}

<figure><img src="/files/wMN8W3DjEBi7NNGPtYmG" alt=""><figcaption></figcaption></figure>

### Authentication & Enrollment

Once the application opens, select the **Login** button at the bottom.

<figure><img src="/files/v8D9hudTxU48VrzKDSst" alt=""><figcaption></figcaption></figure>

You can log in and enroll using one of two methods:&#x20;

* **SSO** (recommended)
* **SSH Key**

<figure><img src="/files/wvu4igkSwzYDtfYxKS1W" alt=""><figcaption></figcaption></figure>

#### SSO (Google OAuth or Microsoft Entra ID)

Run the following command on the instance to enroll the bluedev bouncer before clicking on the **SSO (recommended)**:

{% code overflow="wrap" %}

```shellscript
$ sudo bluedev-bouncer enroll --ca <bootstrap-URL> --password

## Enter the BOUNCER_PASSWORD when prompted
```

{% endcode %}

1. Select the **SSO (Recommended)** option within Cobalt.
2. Provide the bootstrap string URL in the **Bootstrap URL** field.\
   In the following format, and click **Sign in**:

   <pre class="language-shellscript" data-overflow="wrap"><code class="lang-shellscript">https://&#x3C;identity-example>.com#fp=&#x3C;sha256-hex>
   </code></pre>

   <figure><img src="/files/bxLfYhXra0h70fX7xdKj" alt=""><figcaption></figcaption></figure>
3. Click the **Enroll** command inside Cobalt. This action automatically redirects you to your web browser for authentication.
4. Complete the sign-in flow in your browser to bring up and authorize Cobalt. Once Cobalt is successfully authenticated, the following log appears.

   <figure><img src="/files/lxSdyWIWueROzFANYihi" alt=""><figcaption></figcaption></figure>

#### SSH Trust Auth

Select the **SSH key** login option.

<figure><img src="/files/7CSHDZPuri0eh5VHSvt2" alt=""><figcaption></figcaption></figure>

1. Run the following command on the local machine to get the fingerprint (`SHA256: <base 64>`):

   <pre class="language-shellscript" data-overflow="wrap"><code class="lang-shellscript">ssh-keyscan -T 10 -t ed25519 &#x3C;host-ip> | ssh-keygen -lf - 2>&#x26;1
   </code></pre>
2. Insert the Bootstrap string with the following format:

   ```
   <host-ip>#fp=SHA256:<base64>
   ```

   \
   For example:

   ```
   10.101.01.101#fp=SHA256:0x0x0xx00xxx0xx0000x000xxx000000xx0x0x00x00xx0x000x0000xx000x00x/mU
   ```

   \
   Browse and select the required **SSH private key.**

   <figure><img src="/files/4psjD4PobAs6CNVknu6i" alt=""><figcaption></figcaption></figure>

{% hint style="info" icon="notes-sticky" %}
**Note:**

Ensure the same SSH key is present in the `.ssh` folder of the instance's Bluedev profile. For that, run the following commands:

{% code overflow="wrap" %}

```shellscript
## Switch to bluedev user
$ sudo su bluedev

# Create the .ssh directory with correct permissions
$ mkdir -p ~/.ssh
$ chmod 700 ~/.ssh

# Add your local public key to authorized_keys
$ vi ~/.ssh/authorized_keys

# Set secure permissions for the authorized_keys file
$ chmod 600 ~/.ssh/authorized_keys
```

{% endcode %}
{% endhint %}

### Environment Lifecycle Management

{% hint style="info" icon="notes-sticky" %}
**Note:**

BlueRock Bridge (Cobalt) supports a single container environment only.
{% endhint %}

<figure><img src="/files/ico76XgkUjtE9H0DL6AA" alt=""><figcaption></figcaption></figure>

* **Setup Environment**: \
  Click **Setup Environment** to pull and spin up the designated Docker container. Verify that it is running by executing `docker ps` directly on your BlueRock instance.
* **Stop Environment**: \
  Click **Stop Environment** to halt your running container. Verifying the container status on the BlueRock instance will confirm that it has stopped.
* **Start Container**: \
  If an environment has been stopped but not destroyed, a **Start Container** option will be available to restart the existing container and preserve its state.
* **Destroy Environment**: \
  Click **Destroy Environment** to completely purge and delete the container instance from the host.

#### System Tools

<figure><img src="/files/5OxsLgA2BBixZv1yKqQr" alt=""><figcaption></figcaption></figure>

* **Status**: \
  Click this button to view diagnostic metadata regarding the active container, including its current state and container ID.
* **Show Files**: \
  Selecting this option mounts the remote container directory to your local Windows filesystem. This exposes the file structure inside **This PC** as if it were a local directory.
* **Clear Log**: \
  Functions similarly to a terminal `clear` command. It empties the visual logging output console view within Cobalt.
* **Reload**: \
  Used when shifting workloads from one BlueRock environment to another (for example, transitioning from Instance A to Instance B). If the dashboard interface hangs on a cached IP address from a previous session after re-enrolling, clicking **Reload** manually refreshes the configuration and pulls down the updated public IP address and configuration settings.

The bluedev Container mounts on the Windows file system under **Network Location**:

<figure><img src="/files/fyD2hKIIHYd6VMVyhRZD" alt=""><figcaption></figcaption></figure>

### Connecting to Claude Code IDE

To bridge your local Claude IDE environment with the remote container, follow these configuration steps:

1. Manually open your **Claude ID** application.
2. Click on the **Code** menu option.
3. Select **Local**.

   <figure><img src="/files/Jcr2Jfyx3mwT8Mek6zsV" alt=""><figcaption></figcaption></figure>
4. Select **Add SSH Host**.

   <div align="left"><figure><img src="/files/YcVEdZ2EoVJgnUyO6Rrd" alt=""><figcaption></figcaption></figure></div>
5. Enter `cobalt-59` in the **SSH Host** field in the hostname prompt.

   <figure><img src="/files/c0QaIkOQIYAAqGB0WI00" alt=""><figcaption></figcaption></figure>
6. Click **Add SSH Connection**. Any tasks or development scripts created inside this window will now execute directly inside your active remote `bluedev` Docker container.

   <figure><img src="/files/aMNtbbVMMYMUklyVAmN5" alt=""><figcaption></figcaption></figure>

{% hint style="info" icon="notes-sticky" %}
**Note:**

OTEL events are generated by the `blueclaude_sensor` for all the actions done by the coding agent running inside the remote container.
{% 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/archive-v26.23.0/bluerock-bridge-connector-26.23.0.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.