Skip to main content
Code is a special integration: instead of connecting a third-party account, it gives an agent the ability to work directly inside your company’s git repositories — reading code, opening pull requests, and reproducing bugs — through an isolated, disposable environment rather than a live credential the agent could ever see.
Code has no credential of its own. It reuses your company’s existing GitHub connection to reach your repositories, so a GitHub connection must be active before Code can be enabled.

​
Enabling it

1

Connect GitHub

Under Settings → Integrations, connect GitHub if you haven’t already. Code has nothing to authenticate on its own — it borrows this connection.
2

Activate Code

Enable the Code connector for your company. Unlike other connectors, there’s no key to paste — it’s a one-click activation.
3

Grant it to an agent

Grant Code to an agent the same way you’d grant any other connection — see Permissions — with one addition: a repository allow-list.

​
Actions

A read grant scope permits investigate only; implement_ticket and reproduce require read_write, following the same scope rule as every other connector — see Permissions.
All three actions run asynchronously. The agent queues the task and is notified with the result once it completes — it isn’t blocked waiting on a long-running investigation or implementation.

​
Repository allow-list

Access to repositories is deny-by-default, just like actions: a Code grant carries its own allow-list of repositories, separate from and in addition to the action allow-list. An agent with a Code grant but an empty repository list can act on nothing. You manage this list per grant, adding or removing repositories the agent is permitted to touch — an agent can be trusted with one repository and denied every other one your company owns.

​
Isolation

Every Code task — an investigation, an implementation, or a reproduction attempt — runs in its own single-use execution environment, provisioned for the task and discarded when it finishes. Each call starts from a fresh checkout of the repository; nothing accumulates between tasks.

​
Use cases

Bug triage

Point an agent at a vague bug report with investigate and get back a structured report with exact file and line references, before anyone opens an IDE.

Reproduction

Hand an agent a user-reported scenario and let reproduce confirm — or rule out — the bug in an isolated environment, with a clear verdict.

First-draft fixes

Let an agent turn a ticket into a draft pull request with implement_ticket, ready for a human to review, refine, and merge.

GitHub

The connection Code relies on to reach your repositories.

Permissions

The grant model Code’s actions and repository allow-list build on.

Security

How Code’s tasks stay isolated and audited like every other integration call.