Get up and running with Corridor in under 5 minutes.
Get up and running with Corridor in a few quick steps. This assumes you have a Corridor account (sign up at app.corridor.dev) and access to the code repository you want to secure.
In the Corridor web app, you’ll be prompted to connect your GitHub account or organization. Authorize the Corridor GitHub App with the necessary permissions.
Click Connect GitHub and authorize the Corridor GitHub App. You can grant access to All repositories or select specific repos—be sure to include any repos you want Corridor to monitor.
Corridor needs read access to code and permission to write PR comments to perform reviews.
Once GitHub is connected, add a repository as a Project in Corridor.
1
Go to Projects
In the Corridor dashboard, go to Projects and click New Project.
2
Select repository
Select the repo from the list to bring it under Corridor’s protection. You must add a project before Corridor can analyze its code—simply connecting GitHub isn’t enough.
3
Auto-generated guardrails
After adding, Corridor will scan the codebase and automatically generate initial security guardrails tailored to that project.
To get real-time guardrails while coding, install Corridor’s integration for your development environment:
VS Code
Cursor
Claude Code
Factory
Codex
Devin
Devin Desktop
Custom MCP
Open VS Code
Go to the Extensions panel (Cmd+Shift+X or Ctrl+Shift+X)
Search for “Corridor”
Click Install
Reload your editor when prompted
After installation, you’ll see the Corridor icon in your sidebar.
GitHub Copilot users: If your organization manages Copilot through GitHub Enterprise, an admin must enable external MCP servers in the Copilot policy settings before Corridor’s tools will appear.
Cursor has two Corridor integrations. You can use either or both at the same time.Option 1: Cursor Plugin — available in the Cursor Marketplace. Includes the /corridor skill to review code in the background as Cursor Agents work. Use this for a frictionless, Cursor-native experience with the least setup.
In Cursor, open the Agents tab and navigate to the Marketplace
Find Corridor and click Get
Click New Agent and configure it as Local
Invoke the skill in any chat with /corridor
Option 2: Corridor extension — a VS Code-style extension that registers Corridor as an MCP server and runs deterministic hooks. Use this for access to all Corridor features, such as MCP-based tool access, MCP compliance enforcement, or hooks that can block code with critical findings.
Open the Extensions panel in Cursor (Cmd+Shift+X or Ctrl+Shift+X)
Search for “Corridor” and click Install
Reload Cursor and sign in from the Corridor sidebar
See Cursor setup for detailed instructions on both options.
Integrate Corridor with Claude Code via the extension or CLI.Option 1: VS Code or Cursor ExtensionIf you use Claude Code within VS Code or Cursor:
Install the Corridor extension in VS Code or Cursor (see the VS Code tab or Cursor tab above)
Sign in to your Corridor account
The extension automatically configures Claude Code’s MCP settings
Option 2: CLIIf you use Claude Code as a standalone CLI:
If you’re on a Team or Enterprise plan, you can invite colleagues to join your Corridor workspace so they can benefit from the same guardrails and visibility.
1
Open Team Settings
Go to Team Settings → Members.
2
Invite members
Click Invite Member, enter their email, and select a role.
See Inviting Teammates for details. Skip this if you’re an individual user.
That’s it—Corridor is now set up! From this point on:
In the IDE: Your AI assistant (e.g. Cursor or Claude Code) will consult Corridor’s guardrails as you generate code, stopping insecure suggestions
For Pull Requests: Corridor will automatically review new PRs on your connected project. You’ll see comments or checks on the PR if any vulnerabilities are found
Dashboard: You can monitor findings and adjust settings via the Corridor Dashboard
You’ve successfully onboarded Corridor to your project—secure coding can now happen in real-time without breaking your flow.