annsa
Log inStart free

Integration · Repo context

Connect GitHub. Get a spec that knows your code.

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

Start freeSee 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.

02
Pick a repo.

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

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.

04
Two roles, one connection.

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

What you get

Every spec, grounded in your repo.

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

repo · tandem/workspace-app
Files to touch · generated from your connected codebase
repo · connectedspec groundedfiles mapped
agent handoff ready

Asked + answered.

Q1
What does Annsa read from my repo?
Nine signals read per brief — file signatures, .cursorrules/CLAUDE.md, testing patterns, directory structure, open issues, recent merged PRs, tech stack, CI/CD and config files, and README. The LLM prompt then sees five ordered sections: relevant code context, related issues, codebase conventions, testing pattern and directory overview.
Q2
Does Annsa read my source code?
Annsa reads structure and conventions to shape specs, and never changes your code: no commits, pushes or PRs. The one thing it writes is a GitHub issue from a brief, on demand or automatically if you enable it.
Q3
How does GitHub power the Spec map?
Every spec Annsa 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.
Q4
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.

More integrations

annsa

Connect once. Every spec fits.

One repo connection powers spec context, the Spec map, and per-card agent handoff.

Start freeSee Spec →