Connections

​

Three kinds of connection

The Connections page handles three different jobs behind one interface: Source control is what makes Console able to act on your code. Vendor connectors are what let it reason about findings your existing stack has already produced. Integrations are what let it put results where your team works. This page covers the first two; integrations have their own section.

​

Source control

​

GitHub

Install the Console GitHub App for your organization. You can grant access to every repository or pick a subset; the repositories you grant become projects. The App is what powers:

• Cloning repositories into sandboxes
• Pull request triggers firing on open, reopen, and new commits
• Review comments
• Merge gates as required checks
• Opening a pull request from a finding’s suggested fix

See Installation for the install flow.

​

GitLab

Connect a GitLab instance by providing its host URL, the project, and a personal access token.

​

Vendor connectors

Console connects to the security and IT tools you already run, so agents can reason about the findings already sitting in them. Open Connections, add a connection, and search the connector catalog. Connectors are grouped by category: The catalog is searchable by vendor name or slug, and a connector spanning more than one category appears under each — AWS Inspector shows up under both AppSec and VMS, for instance. Completing a connection walks you through that vendor’s own authorization flow. Console stores the resulting connection and never handles the underlying vendor API key directly — requests are brokered server-side.

​

Integrations

Integrations connect the third-party apps your team works in, so agents can post to Slack, file Jira or Linear issues, and read and write Confluence, Notion, and Google Docs. They live in the Agent Tools section of the Add Connection dialog. An organization admin connects each app once, as a bot account you own, and every agent in the organization gets that app’s tools. See Integrations for what each app exposes, and connecting an app for the flow.

​

Which connections do you need?

​

Troubleshooting

A repository isn’t available as a project. The GitHub App installation probably doesn’t include it. Adjust the installation’s repository access. An output shows Failed on a run. Confirm the App is still installed for that repository and has permission to write checks and pull request comments. See checking delivery. The connector catalog is empty or won’t load. The catalog is fetched when you open the dialog, so a transient upstream failure shows there without affecting the rest of the page. Retry.

​

Next steps