> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-code/scanning/ox-cli-1/authenticating-ox-cli/connect-ox-cli-with-vibesec.md).

# Connect OX CLI with VibeSec

When you already have VibeSec in a supported IDE, you can use the IDE's authentication to run an OX CLI scan without configuring the CLI separately. After the scan completes, the CLI continues using its configured authentication method.

VibeSec authentication is supported for the following IDE integrations:

* Claude Code
* Cursor
* Visual Studio Code with GitHub Copilot

### Before you begin

Make sure that:

* The OX CLI is installed.
* A supported OX IDE integration is installed and authenticated.
* VibeSec is enabled in the IDE.

> **Note**
>
> The OX IDE integration must already be authenticated. If no valid authentication token is available, the scan fails.

### Run a scan with VibeSec authentication

Run the following command:

```bash
ox-cli scan --use-vibesec-auth
```

The CLI automatically searches for authentication credentials stored by supported IDE integrations in the following order:

1. Claude Code
2. Cursor
3. Visual Studio Code with GitHub Copilot

The first valid authentication token and its associated OX API endpoint are used for the current scan.

This authentication applies only to the current scan. Your configured CLI authentication method, such as OAuth or an API key, remains unchanged.


---

# 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.ox.security/ox-code/scanning/ox-cli-1/authenticating-ox-cli/connect-ox-cli-with-vibesec.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.