For the complete documentation index, see llms.txt. This page is also available as Markdown.

BlueRock Connector - Windows

The BlueRock Connector application for Windows establishes a secure bridge between local AI IDEs (Claude Code or Codex) and the remote BlueRock sandbox. The application natively handles SSO and SSH key authentication, local port forwarding, and container lifecycle management to enable a fully remote coding workspace.

Prerequisites

Software and Client Applications

  • BlueRock Connector App: Contact BlueRock support to obtain BlueRock_Connector_win64.exe.

  • OpenSSH Client: The client must be installed and added to the system PATH (e.g., C:\Windows\System32\OpenSSH\).

notes

Note:

The OpenSSH Client is an optional Windows feature and is frequently removed from hardened corporate images.

System Requirements

Operating System:

Windows 11 (24H2 or later) is required for file transfers between the local machine and the BlueRock environment.

lightbulb-exclamation-on

Network and Security

  • Virtual Private Network (VPN): If the BlueRock instance resides on a private network, active VPN connectivity is required to reach the instance.

  • Endpoint Protection: On desktop clients running firewalls or security software, allow port 2259 for inbound connections. The BlueRock Connector application runs a listener service on port 2259 and the loopback interface. The traffic is internal and never leaves the device.

Installation

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

notes

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.

Authentication and Enrollment

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

  2. Select Continue on the welcome screen.

  3. Choose one of the following authentication methods:

    1. Sign in with BlueRock Also, known as Single Sign On (SSO) login option.

      1. Select the Sign in with BlueRock option then select Next.

      2. Provide the bootstrap string URL in the Enrollment URL field and enter the public DNS or IP address of the BlueRock host in the Dev host field. Click Sign in.

      3. Complete the sign-in flow in the web browser to authorize the application.

    2. SSH Key

      1. Select the SSH key option then select Next.

      2. Run the following command on the local machine to obtain the fingerprint:

      3. Enter the Bootstrap string in the application using the following format: <host-ip>#fp=SHA256:<base64> (For example: 10.101.01.101#fp=SHA256:0x0x...)

      4. Click Browse, select the required SSH private key, and click Install Key.

notes

Note:

Ensure the same SSH public key is present in the .ssh folder of the instance's Bluedev profile. Run the following commands on the BlueRock instance to configure the key:

  1. Then click Close and Continue to Connector to proceed working with the connector app.

Environment Lifecycle Management

Create Sandbox

Select the Create sandbox button to initialize the remote container.

Stop Sandbox

Click Stop Sandbox to halt the running container.

Destroy Environment

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

Click Destroy Sandbox - confirm buttong in the prompt to destrory the sandbox and its files completely.

Connecting AI Tools and Workspace Integration

Connecting to Claude Code IDE

  1. Select the Connect Claude button in the Connector app.

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

  3. In the Claude Code IDE:

    1. Click the Code menu option.

    2. Select Local > SSH > Add SSH Host...

    3. Enter cobalt-59 only in the SSH Host field, with the other details as per the requirements, and click Add SSH Connection.

Then Claude Code will SSH into the instance, and any tasks or development scripts created inside this window will now execute directly inside your active remote bluedev Docker container.

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.

Connecting to Codex

  1. Select the Connect Codex button in the Connector app.

  2. Follow the on-screen dialog instructions and click the provided link to authenticate. A one-time code is also present to enter while setting up an OpenAI account.

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

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

  5. Upon completion of OpenAI account setup, the BlueRock Connector 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 to create a new remote project.

  8. Select cobalt-59 and click Add. Add the connection as a project to the Codex workspace.

  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 and Script Output

  1. In the connected Claude IDE or Codex environment, provide a prompt to create a basic "Hello World" Python script to verify the session.

  2. Review and verify the script output directly within the IDE's terminal or shell.

Browsing Remote Sandbox Files via System File Explorer

  1. In the BlueRock Connector application, select the Browse Files option.

  2. View and interact with the remote files directly within Windows Explorer.

    The bluedev container mounts natively on the Windows file system under Network Locations.

Maintenance and Troubleshooting

Exporting Connector Logs

To troubleshoot issues, export the application logs directly from the system tray. Right-click the BlueRock Connector icon in the System Tray and select Export Logs.... Save the generated log file to a preferred location.

Resetting Connector Configuration

Select Reset in the Sandbox dialog box.

Then confirm the prompt to clear the current configuration.

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.

  • After stopping the container

  • After destroying the container

Last updated