BlueRock Connector for Claude and Codex IDE

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

Setup and Configuration Workflow

Follow the complete deployment path below, or jump directly to the required phase:

1. Prerequisites

2. Installation (Windows)

3. Authentication & Enrollment

   1. SSO (Google OAuth or Microsoft Entra ID)

   2. SSH Key

4. Environment Lifecycle Management

5. Connecting AI Tools & Workspace Integration

   1. Connecting to Claude Code IDE

   2. Connecting to Codex

   3. Verifying Session Execution & Script Output

   4. Browsing Remote Sandbox files via System File Explorer

6. Maintenance & Troubleshooting

Prerequisites

• Claude Code IDE

• Codex

• BlueRock Connector app (Contact BlueRock support to get the BlueRock Connector app)

  • For Windows: BlueRock_Connector_win64.exe

  • For macOS: BlueRock-Connector-notarized.zip

Installation (Windows)

Locate the BlueRock_Connector_win64.exe application and double-click to run it.

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.

Access the BlueRock Connector from the System Tray as well.

Authentication & Enrollment

Once the application opens, select the Set Up Connector button.

Then select Continue on the next screen

Log in and enroll using one of two methods:

• SSO (recommended)

• SSH Key

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):

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

## Enter the BOUNCER_PASSWORD when prompted

1. Select the SSO (Recommended) option.

2. Provide the bootstrap string URL in the Sign-in URL field in the following format: https://<identity-example>.com#fp=<sha256-hex>, and enter the public DNS of the BlueRock host in the Sandbox host field. Then click Sign in:

   
3. 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. Once successfully authenticated, the following log appears.

   

SSH Key

Select the SSH key login option.

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

   ssh-keyscan -T 10 -t ed25519 <host-ip> | ssh-keygen -lf - 2>&1

2. Insert the Bootstrap string in 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, and select Install Key.

Note:

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

## Switch to root user
$ sudo su

## Then 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

After this, the app will validate and authenticate based on the SSH Key.

Environment Lifecycle Management

Note:

BlueRock Connector app supports a single container environment only.

• Creating and Initializing a BlueRock Sandbox Select the Create sandbox button to create a sandbox.

  
• Monitoring Active Sandbox Status and Session Expiration Verify that it is running by executing docker ps directly on your BlueRock instance.

  
• Extend session duration In the Create Sandbox dialog box, click Extend the signed-in session.

• Stop Sandbox: Click Stop Sandbox to halt your running container. Verifying the container status on the BlueRock instance will confirm that it has stopped.

  
• Restart Container: If an environment has been stopped but not destroyed, a Start Sandbox option is available to restart the existing container and preserve its state.

• Destroy Environment: Click Destroy Sandbox to completely purge and delete the container instance from the host.

  

  It will prompt to confirm destroying the sandbox completely.

  

Connecting AI Tools & Workspace Integration

Connecting to Claude Code IDE

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

1. Select the Connect Claude button.

   
2. Select Open Claude Desktop and follow the instructions given on the screen.

   
3. In the Claude IDE:

   1. Click on the Code menu option.

   2. Select Local.

      
   3. Select Add SSH Host.

      
   4. Enter cobalt-59 in the SSH Host field in the hostname prompt.

      
   5. Click Add SSH Connection. Any tasks or development scripts created inside this window will now execute directly inside your active remote bluedev Docker container.

      

Note:

OTEL events are generated by the blueclaude_sensor for all the actions done by the coding agent running inside the remote container.

Connecting to Codex

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

1. Select the Connect Codex button.

   
2. Follow the instructions given in the dialog screen. Click the link given here. On this screen, a one-time code is also present to enter while setting up an OpenAI account.

   
3. Authenticate with the OpenAI/ChatGPT account on the default browser.

   
4. Enter the one-time code and select Continue.

   
5. Upon completion of OpenAI account setup, the BlueRock Bridge app gives a new prompt to Open Codex Settings.

   
6. In Codex, navigate to Connections > select SSH > click Add.

   

7. Select Remote and click Next.

   

8. Select cobalt-59 and click Add.

   

9. In the New Remote Project pane, select cobalt-59 from the Remote dropdown and select Add Project.

Once the project connects successfully, it will be added in the SSH section

Then use it as a project in the Codex workspace.

Verifying Session Execution & Script Output

In the Claude IDE or Codex, give a prompt to create a hello Python script to verify the session.

Example of verifying the script output in the Claude desktop shell

Browsing Remote Sandbox Files via System File Explorer

Select Browse Files

In Windows Explorer, it will open the files

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

Maintenance & Troubleshooting

• Resetting BlueRock Connector Configuration: Reset the BlueRock Connector with the Reset option in the Sandbox dialog box.

  

  Then confirm the reset.

  

• Re-authenticating After Reset or Expiration When a session expires or after stopping/destroying containers and resetting configuration, remote network locations automatically unmount, and Docker containers terminate. Re-run Authentication and Sandbox Creation to establish a new session. On the Windows file system,

  • After stopping the container

    
  • After destroying the container

    

• Access the BlueRock Connector from the System Tray as well.