GitHub

Your work in motion, read in plain English.

Catch up across your repositories, find the change you half-remember, get oriented in an unfamiliar project — and, when you ask, open an issue, a branch, or a pull request. You decide how far it reaches.

The orientation you'd write for yourself — if you ever remembered to.

What it does

  • Catch up across your repos. Pull requests opened, issues filed, notifications worth knowing about — 1Presence reads across the repositories you own and contribute to and tells you the shape of the week in plain English.
  • Find the change without the commit hash. Ask for the moment a function changed, a config was added, a bug was fixed — it searches code, commits and pull requests and summarises what landed and where.
  • Get oriented before you have to. Coming back to a project after a break? It reads the README, the docs folder and the recent tree, and gives you the lay of the land.
  • Open work when you ask. File an issue, create a branch from any base, or open a pull request — from the conversation, on request.

Reads the repo, not just the file

1Presence can list a directory or the full tree, read a file at any branch or tag, and search across repositories — so "what does this project do and where does the auth live" is one question, not an afternoon of clicking. Connected repos also sit under Connected in your vault sidebar, where a file opens inline and a folder unfolds in place.

Wire it to a scheduled workflow and it becomes a morning digest: what merged overnight, which issues mention something you care about, which PRs are waiting on you — delivered before you open the laptop.

Try asking

From orientation to action, in chat:

What happened across my repos this week?

Reads PRs, issues and notifications and gives you a plain-English digest.

Find where we changed the rate-limit logic.

Searches code and commits, summarises the change, and names the PR that landed it.

Explain what the payments service does — read its README and structure.

Reads the README and the tree and orients you in a few sentences.

Open an issue on the api repo: "429s on the export endpoint", label bug.

Creates the issue with your title, body and label, then links it back.

Read-only, or let it write

Connection is through GitHub's own login. You choose the level: your public repositories, read and write — issues, branches, pull requests, file commits — or full access that adds your private ones.

Writing happens only when you ask for it — there is no autonomous committing, and nothing touches a repo you have not pointed it at. Changing a file that already exists confirms every time. Tokens, grants and revoking work the same for every connector: see how permission works.

How access works

Read the project. Act on request.

Browse repos, search code and commits, and get oriented in plain English — then, when you grant it, open issues, branches and pull requests from the conversation. Private repos stay private until you choose full access.

Start a conversation.

Free to try. No credit card. Just you and your agent.

Works on any device. Start chatting straight away.

Last reviewed