Circuit
Log inSign up
Integration · Repo context

A spec that already knows your code.

Connect your repo once. Circuit pulls five prompt sections, drawn from sixteen GitHub signals — your conventions, your file structures, your testing pattern — and weaves them into every spec. The spec arrives implementable, not aspirational.

Connect GitHub once and every spec is shaped to your codebase.

Connect GitHub →See Spec →
— How it connects —

One connection, two roles.

Sign in, pick a repo, and the same connection powers spec context and briefs out.

01
Connect with OAuth.

Sign in with GitHub. State token with ten-minute TTL, HMAC-SHA256 signed.

Connection
oauth_states · TTL 10:00
02
Pick a repo.

Single repo per connection. Circuit pre-selects the first you have access to.

Connection
spacetour/spacetour-app
03
Optional toggles.

A one-time refresh of your existing briefs against the newly-connected repo, plus an optional auto-create-issue toggle when briefs generate. Both off by default.

Connection
Refresh briefs · Auto-issue · off
04
Two roles, one connection.

Repo context for every spec, plus a hook destination for briefs out — same connection drives both.

Connection
Context in · Briefs out
— What you get —

Every spec, grounded in your repo.

The repo connection feeds spec generation, the Spec map and the Files-to-Touch section.

Spec map, generated.

The Codebase view of the Spec map is built from the Files-to-Touch section of every spec. Connect GitHub and the whole map lights up.

Five prompt sections, drawn from sixteen GitHub signals.

RELEVANT CODE CONTEXT · RELATED ISSUES · CODEBASE CONVENTIONS · TESTING PATTERN · DIRECTORY OVERVIEW.

Files-to-Touch, pre-filled.

Every spec carries a Files-to-Touch section grounded in your actual codebase — not invented file paths.

— The proof —

Connect once. Every spec fits.

OAuth state stored in an oauth_states table with 10-minute TTL and HMAC-SHA256 signature. Connect once; the repo connection powers spec generation, the Spec map, and per-card handoff to Cursor and Claude Code.

— Questions —

Asked and answered.

What does Circuit read from my repo?

Sixteen signal types fetched per brief — repository, README, tech stack, directory structure, recent commits, open issues, related issues, open PRs, recent merged PRs, relevant files, file signatures, import graph, AI config (CLAUDE.md / .cursorrules), a sample test, contributing guide, GitHub Actions and config files. The LLM prompt then sees five ordered sections: RELEVANT CODE CONTEXT, RELATED ISSUES, CODEBASE CONVENTIONS, TESTING PATTERN, DIRECTORY OVERVIEW.

Does Circuit read my source code?

Read scope only. Circuit reads structure and conventions to shape specs — never writes to your repo without an explicit action (push to issue, create PR comment, and so on).

How does GitHub power the Spec map?

Every spec Circuit generates includes a Files-to-Touch section. The Spec map's codebase view is the union of those file paths — so the more specs you write, the richer the map.

Can the Cursor and Claude Code handoffs work without GitHub?

No. The handoff dispatches the agent against a specific repo, so a GitHub connection is required. The buttons are hidden on roadmap cards until you connect.

Connect once. Every spec fits.

Connect GitHub →See Spec →
RelatedCursor · Claude Code · Linear · All integrations

Part of Circuit’s autonomous product intelligence stack — see the full picture.