7 min read
Pin repositories as context
Give an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.
- 01
Find the repository the agent keeps looking up
Read a few runs and notice which codebase the agent reaches for every single time — the service it reviews, the repo whose conventions it checks. That is the repository worth pinning.
- 02
Pin it as an integration resource
An integration resource scopes a connection down to one specific thing: one repository rather than the whole GitHub org. The pin carries the integration it belongs to, so credentials come along and stay server-side.
- 03
Attach it to the workflow or chat
Pinned repositories become standing context for the agent. It knows the codebase exists before you mention it, and it starts from the repo instead of searching for it again on every run.
- 04
Use pinning to narrow reach
Pinning is a scoping decision as much as a convenience one. An agent pinned to one repository has a smaller surface than an agent roaming the whole org, and its prompts get shorter as a result.
- 05
Let memory build on top of it
Pinned repositories give the agent the same starting context every run. Memory carries what it learned across runs — escalation rules, schema shapes, naming conventions. Together they mean the fifth run knows more than the first without you rewriting the prompt.
Keep going
Next in the track
10 min
Run your first agent
Describe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.
12 min
React to GitHub events
Start an agent the moment a pull request opens, a build goes red, or a tag lands — filtered down to exactly the events you want it on.
9 min
Share with your team
Hand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record of what happened.
Templates
Put it to work
Templates that use what this guide covers.
Engineering
Pull request reviewer
Reviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.
Engineering
Incident postmortem drafter
Reconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.
Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.