> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corridor.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Uninstall Corridor

> Remove Corridor from your organization: IDE extensions, the CLI, cloud agents, the GitHub App, integrations, and credentials.

Follow the steps in order. If you deployed Corridor with MDM, also complete [Additional steps for MDM](#additional-steps-for-mdm).

> [!NOTE]
>
> Uninstalling doesn't delete your Corridor team or its data. To cancel billing, see [Cancel your subscription](#optional-cancel-your-subscription).

## Prerequisites

* **Owner** or **Admin** role on your Corridor team
* Owner access to each GitHub organization with the Corridor GitHub App

## Uninstall Corridor

**1. Remove the Corridor Review required check**

If **Corridor Review** is a required status check, remove it first. Otherwise pull requests can't merge after the GitHub App is gone.

In GitHub, edit the branch protection rule (**Settings → Branches**) or ruleset (**Settings → Rules → Rulesets**), remove **Corridor Review**, and save.

**2. Remove Corridor from developer machines**

Run the Corridor uninstaller on each machine. It removes the CLI, hooks, MCP entries, agent rules, and plugins for every agent, and deletes `~/.corridor`.

```bash macOS and Linux theme={null}
curl -fsSL https://app.corridor.dev/cli/uninstall.sh | bash
```

```powershell Windows theme={null}
& "$env:USERPROFILE\.corridor\bin\corridor.exe" uninstall --non-interactive
```

Then remove the IDE extension and restart each tool:

> [tab] VS Code
>
> ```bash theme={null}
> code --uninstall-extension corridor.Corridor
> ```

> [tab] Cursor
>
> ```bash theme={null}
> cursor --uninstall-extension corridor.Corridor
> ```
>
> If you installed the Corridor Cursor Plugin, uninstall it from the **Marketplace** in the **Agents** tab.

> [tab] Windsurf
>
> ```bash theme={null}
> windsurf --uninstall-extension corridor.Corridor
> ```

> [tab] Devin Desktop
>
> Open the Extensions view, find **Corridor**, and click **Uninstall**.

> [tab] Claude Code, Factory, Codex
>
> The uninstaller removes Corridor from these agents. Restart them.

> [tab] Custom MCP
>
> Remove the `corridor` entry that points to `https://app.corridor.dev/api/mcp` from your MCP client configuration.

**3. Remove Corridor from cloud agents**

In each Cursor, Claude Code, Codex, or Devin environment that runs Corridor, remove the Corridor setup script and delete the `CORRIDOR_API_KEY` secret. Otherwise Corridor is reinstalled on the next run.

**4. Disconnect source control**

> [tab] GitHub
>
> In your GitHub organization, go to **Settings → GitHub Apps**. Next to **Corridor**, click **Configure**, then **Uninstall**. Repeat for each organization.

> [tab] GitLab
>
> Email [support@corridor.dev](mailto:support@corridor.dev) with your team name and GitLab group. Support disconnects the group, deletes the webhooks Corridor created, and revokes its access tokens.

**5. Disconnect other integrations**

Remove the Corridor app from Slack and Linear, and from Okta or Microsoft Entra ID if you set up SSO.

**6. Revoke Corridor credentials**

The uninstaller only revokes the token created by `corridor login`. Delete the rest:

* **Settings → User API Tokens** for each user, including tokens named `MDM Provisioned - <platform> - <serial>`
* **Configuration → Team-Owned API Keys**
* **Teams → Universal Team Tokens**

Also delete stored copies of `CORRIDOR_API_KEY` in CI secrets and shell profiles.

## Additional steps for MDM

Do these alongside the steps above.

**1. Stop provisioning**

In your MDM, disable or unscope the Corridor provisioning policy. Then delete your Universal Team Tokens in Corridor under **Teams → Universal Team Tokens**, so the provisioning script can't create new tokens.

**2. Run the uninstall script**

The uninstall script removes the IDE extensions and runs the Corridor uninstaller for the signed-in user. It exits `1` if anything remains, so your MDM reports the device as failed.

```bash macOS theme={null}
curl https://raw.githubusercontent.com/CorridorSecurity/CorridorSecurity/refs/heads/main/mdm/uninstall-macos.sh -o uninstall-macos.sh
```

```bash Windows theme={null}
curl https://raw.githubusercontent.com/CorridorSecurity/CorridorSecurity/refs/heads/main/mdm/uninstall-windows.ps1 -o uninstall-windows.ps1
```

Deploy it the same way you deployed the provisioning script:

> [tab] JAMF
>
> Add `uninstall-macos.sh` under **Settings → Computer management → Scripts**. Create a policy that runs it **Once per computer** on your provisioned computers.

> [tab] Fleet
>
> Add `uninstall-macos.sh` under **Controls → Scripts** and run it on your provisioned hosts.

> [tab] Kandji / Iru
>
> Add `uninstall-macos.sh` as a **Custom Script** in the **Library**. Set it to **Run once per device** and assign it to your Blueprints.

> [tab] Intune (macOS)
>
> Add `uninstall-macos.sh` under **Devices → Scripts and remediations → Platform scripts**. Set **Run script as signed-in user** to **No**.

> [tab] Intune (Windows)
>
> Add `uninstall-windows.ps1` under **Devices → Scripts and remediations → Platform scripts**. Set **Run this script using the logged on credentials** to **Yes**.

**3. Remove the provisioning files**

After the uninstall script runs, delete the Corridor provisioning script, policy, and configuration profile from your MDM.

> [!TIP]
>
> To audit devices without removing anything, set `CHECK_ONLY=true` (macOS) or `$CHECK_ONLY = $true` (Windows) at the top of the script. It exits `0` when Corridor is fully removed and `1` otherwise.

## Verify removal

* **On each device:** run the uninstall script with `CHECK_ONLY` set. Or check that `~/.corridor` no longer exists.
* **In Corridor:** in **Governance → Team Compliance**, the **active devices** count is `0`. The count covers machines that run Corridor hooks. IDE extensions without hooks and cloud agents are not included. `corridor uninstall` marks a device **uninstalled**, and the uninstall script runs it. A device that is silent for 14 days counts as **inactive**. The token pages in the last step are empty.
* **In GitHub:** Corridor isn't listed under **Settings → GitHub Apps**, and new pull requests get no **Corridor Review** check.

## (Optional) Cancel your subscription

Cancel your subscription in **Team Settings → Billing**. See [Billing](https://docs.corridor.dev/administration/billing.md#cancellation).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.