> ## 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.

# Corridor Agent

> A security teammate you can talk to. Ask about findings across your projects, get explanations, and have it fix issues and open pull requests.

<Note>
  Corridor Agent is available on **Enterprise** plans.
</Note>

Corridor Agent is a security teammate you can talk to. Ask it what's broken across your projects, have it explain a finding, or tell it to fix a security issue and watch it open a pull request for you. It is the recommended way to talk to Corridor, in the dashboard and in Slack.

A few things to ask Corridor Agent:

* "What are our open critical and high findings?"
* "Explain this finding and how to fix it."
* "Fix the SQL injection in checkout and open a PR."
* "Check whether that same SQL injection pattern exists in our other services."
* "Give me a report of findings by severity."

## Choosing a scope

When you start a session, pick which projects it covers:

| Scope             | How to select it                               | What the Agent covers                                        |
| ----------------- | ---------------------------------------------- | ------------------------------------------------------------ |
| Single project    | Pick one project                               | That project only                                            |
| Multiple projects | Pick two or more projects                      | The projects you selected                                    |
| All projects      | Pick all projects, or leave the selector empty | Every project your team owns, including projects added later |

A common pattern is to start with all projects to triage, then open a single-project session to remediate.

## What you can do

* **Investigate findings**: Ask about open findings across every project in scope, compare severity across repositories, or check whether a pattern from one service shows up in another.
* **Fix code**: Tell the Agent to fix an issue. It proposes a diff you can review in the session and turn into a pull request.
* **Generate reports**: Ask for a summary of findings by severity, project, or state.
* **Attach files**: Add files to a session to give the Agent extra context.

## How it works

The Agent reads findings for every project in scope through Corridor's built-in tools, so it can answer questions that span repositories. For code-level questions and fixes, it works in a repository from your scope. For projects connected through GitHub, it can also read the source of the other in-scope repositories on demand with read-only access. When it changes code, it produces a diff you can review in the session and turn into a pull request.

<Note>
  On GitHub, the Agent can read source across every repository in scope. On GitLab, it works with findings across your scope but reads code only in the repository it is working in.
</Note>

## Corridor Agent in Slack

Mention **@Corridor** in a public channel to ask about a finding or dig into an issue. Corridor replies in the thread and keeps its context, so you can ask follow-ups. Sessions started from Slack also appear in the Agent tab. See the [Slack integration](/integrations/slack) page for setup.

## Getting started

1. Open the [Agent tab](https://app.corridor.dev/agent) in the dashboard.
2. Pick your projects: one, several, or all of them.
3. Ask your first question.

If you prefer to work from Slack, mention **@Corridor** in a public channel.

## Next steps

<CardGroup cols={2}>
  <Card title="Findings" icon="magnifying-glass" href="/features/findings">
    View and manage security findings
  </Card>

  <Card title="Slack integration" icon="slack" href="/integrations/slack">
    Talk to Corridor from your Slack workspace
  </Card>
</CardGroup>