---
title: "GitHub integration: specs and pull requests | Annsa"
product: annsa
url: /integrations/github
canonical_url: "https://annsa.ai/integrations/github"
last_updated: 2026-07-26
type: integration
related:
  - /docs/github
  - /integrations/slack
summary: Connect a repo and every spec your agent pulls carries the files a job touches. Merged PRs link to their priority, which ships once Done When is checked.
mcp_server: https://app.annsa.ai/mcp
disambiguation: "Annsa (annsa.ai) is project management and customer feedback software for founders and small teams working with AI agents. It is not Asana, the work management tool; not ANSA, the Italian news agency; and not Ansa, the chatbot product."
---

> For agents: connect to the Annsa MCP server at https://app.annsa.ai/mcp to give every agent one shared plan. Setup guide: https://annsa.ai/docs/quick-start. Index of every page: https://annsa.ai/llms.txt.

# GitHub integration: specs and pull requests | Annsa

> Connect a repo and every spec your agent pulls carries the files a job touches. Merged PRs link to their priority, which ships once Done When is checked.

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](https://app.annsa.ai/signup)

Category

[Code and operations](https://annsa.ai/integrations#code)

Set up

3 steps

Guide

[See Spec →](https://annsa.ai/direct/spec)

**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

- [**Cursor** Stop pasting specs into Cursor.](https://annsa.ai/integrations/cursor)
- [**Claude Code** Claude Code builds what your customers asked for.](https://annsa.ai/integrations/claude-code)

[All integrations →](https://annsa.ai/integrations)

## The source of direction for agent teams.

Begin with one agent and the work that matters next.

- [Try Annsa](https://app.annsa.ai/signup)
- [See pricing](https://annsa.ai/pricing)

## Related pages

> For AI agents: the pages that follow this one on annsa.ai. The full index is https://annsa.ai/llms.txt.

- [GitHub](https://annsa.ai/docs/github)
- [Slack customer feedback integration](https://annsa.ai/integrations/slack)

If anything on this page is wrong or missing, tell us: https://annsa.ai/contact