annsa
Log inTry Annsa

GitHub

Your agents know your code. You know what shipped.

Connect a repo once, and every spec your agent pulls carries its context.

Try Annsa
Set up
3 steps
Priorities 5 to work on
Improve retention Keep customers past month one3 to work on
1Add dark mode#12
2Fix mobile checkout#14
3Dark mode charts#13
Drive trials Trial to paid2 to work on
4Fix onboarding step 2#9
5Launch email for dark mode#16
repo · tandem/workspace-appFiles to touch · from your connected reposrc/theme/tokens.tssrc/components/Chart.tsxsrc/app/Settings.tsx agent context ready

Files to touch, from your repo. The next spec your agent pulls names the files it will likely change.

One repo, two jobs done.

  • Specs that fit your code.Your agent gets your tech stack, likely files, related pull requests and your AGENTS.md, CLAUDE.md or .cursorrules.
  • 16 repo signals, read for you.README, commits, issues, tests and CI, so the agent starts where your code is.
  • Merged work, linked.A merged pull request links to its priority. It ships once every Done When line is checked.

Sign in, pick a repo.

Context refreshes after each merge to your default branch.

  1. Connect the repo.Settings → Integrations → GitHub → Connect, then authorize Annsa and pick a repository.
  2. Name the priority in your PRs.Add an Annsa-Spec: line or #N to the pull request body.
  3. Check it worked.Ask your agent for a spec. Files to touch should name real paths.

Questions people ask.

Which GitHub events does Annsa listen for?

Three: pull requests, closed issues and deploy status.

Does Annsa write to my repo?

Only issues, when you ask or turn that on. It never changes code or deploys.

Who writes the spec?

You, your agent over MCP, or Ask, which reads your repo when asked. Never Annsa on its own.

Goes well with

The source of direction for agent teams.

Begin with one agent and the work that matters next.

Try AnnsaSee pricing