> 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/bluerock-connector-for-claude-and-codex-ide.md).

# BlueRock Connector for Claude and Codex IDE

BlueRock Connector is available for both Windows and macOS, acting as a secure bridge between local AI IDEs ([Claude Code](https://claude.com/product/claude-code) or [Codex](https://openai.com/codex/)) and the remote BlueRock sandbox. It enables a fully remote coding workspace by launching and managing the `bluedev-container` on the BlueRock Host VM. Additionally, the application handles local port forwarding and supports secure SSH logging into the remote container using Sign in with BlueRock or SSH key-based authentication.

### Key Capabilities

* **Secure Enrollment:** \
  Authenticates securely using Sign in with BlueRock or SSH keys.
* **Environment Management:** \
  Creates, stops, restarts, or destroys the remote BlueRock sandbox directly from the local system tray or menu bar.
* **Seamless IDE Integration:** \
  Automatically configures local listener ports (e.g., port 2259) to bridge the local workspace with the remote container.

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

Core functionality and workflows remain identical across both Windows and macOS, despite adapting to the native operating system interface.
{% endhint %}

### Supported Platforms

Select the operating system to view the complete guide on getting started and working with the Connector:

* [Windows](/bluedev-container/bluerock-connector-for-claude-and-codex-ide/bluerock-connector-windows.md)
* [macOS](/bluedev-container/bluerock-connector-for-claude-and-codex-ide/bluerock-connector-macos.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluerock.io/bluedev-container/bluerock-connector-for-claude-and-codex-ide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.