Connectors

Repositories and code

Index a local checkout and optionally connect GitHub so answers cite real files and lines.

7 min read

Local repositories (stay on your computer)

  1. Clone or open the product repository on this computer.
  2. In Arcus: Settings → Integrations → Local repositories (or Settings → Indexing).
  3. Add the folder. Example: ~/src/spinnaker or C:\Users\you\src\spinnaker.
  4. Wait for indexing to finish. The index never leaves this computer.
  5. Start an investigation. Evidence should name a file and line from that folder when code is involved.
Investigation citing local repository files while drafting a bug
Investigations cite files from the local index.

GitHub (optional)

  1. In Settings → Integrations → GitHub, sign in in the browser or paste a personal access token with repo read scope.
  2. Use GitHub search when the checkout is not on this machine. Prefer the local index for private monorepos.

Privacy

Only the snippets an answer needs are sent to your org’s AI provider with the question. The full index stays local. See Security, DPA and subprocessors.

Next

How investigations work
What Arcus reads, how it reaches a root cause, and how to check its work.
Code panel
Open the exact file and line Arcus cited, without leaving the case.
Security, DPA and subprocessors
Where to find the security overview, the DPA and the subprocessor list.