Notifications and following

Hear what happens where you work

Follow a repository, an organization or a person. Pushes, changes, failed runs and new repositories in what you follow come to your notifications, and so do comments on your work and every @mention of you.

RegisterRead the docs

Following

Repositories, organizations and people

Follow a repository you can read from its page or from any list of repositories, Explore included. Follow an organization or a person from their page: a person hears that you did, and their profile counts it. The Following page has a tab each for repositories, organizations and people, with Unfollow on every row. A repository you can no longer read drops out, and tells you nothing until you can read it again.

Following
RepositoriesOrganizationsPeople
  • Acme @acme12 repositoriesUnfollow8
  • Infra @infra4 repositoriesUnfollow3

Notifications

What happens in what you follow

A repository you follow tells you of each push to its default branch, with how many commits, of each change opened, merged or closed, and of each run that fails. An organization you follow tells you of each repository made or forked into it. You don't hear of what you did yourself, or of what an agent did for you, except a failed run. Unread ones have a dot and are in bold, the bell at the top counts them, and opening one marks it read and takes you to it.

Notifications
Mark all as read
  • bob pushed 3 commits to mainacme/web · 4 min ago
  • Run #41 failed: ciacme/web · 12 min ago
  • carol merged #12: Export invoices as CSVacme/web · 2 h ago
  • dave created billing-api in acmeacme/billing-api · 5 h ago

Comments and mentions

Told by name, followed or not

A comment on a change tells its author and everyone who commented on it before. A comment on a commit tells its author and committer, when their email is verified on an account, and the thread's earlier commenters. An @username in either tells that person once, as a mention, but not inside backticks, an email address or a path. You also hear when someone follows you or what's yours, and when a deployment waits for your review. Nobody hears of their own comment, or of a repository they can't read.

acme/web › Changes › #12

dave

@bob, can you check the rounding here? @billing in the config is only a placeholder.

  • → bobdave mentioned you in #12: Export invoices as CSV
  • → caroldave commented on #12: Export invoices as CSV

People, not tokens

For people, in the web app

Following and notifications need a web session: tokens, agents and apps can't follow anything or read notifications, and the API refuses them. Nothing is sent by email; notifications are behind the bell. Agents hear what concerns them in their MCP sessions instead: a task handed to them, a review or a check finishing, a reply to their comment. With any credential, GET /repos?affiliation=following lists the repositories you follow.

~/web
$ curl -H "Authorization: Bearer $(bscope agent token --name claude-code)" https://api.branchscope.example/v1/me/notifications
{"error":{"code":"forbidden","message":"tokens can't do this; sign in to the web UI"}}
$ curl -X PUT -H "Authorization: Bearer $BRANCHSCOPE_TOKEN" https://api.branchscope.example/v1/orgs/acme/follow
{"error":{"code":"forbidden","message":"tokens can't do this; sign in to the web UI"}}
$ curl -H "Authorization: Bearer $BRANCHSCOPE_TOKEN" "https://api.branchscope.example/v1/repos?affiliation=following"
{"data":[{"repo":"acme/web",…,"followers":8,"following":true}],"nextCursor":null}

Follow what you work on

Press Follow on a repository or an organization, and from then on what happens in it is in your notifications.

Register