A step-by-step walkthrough for connecting GitHub so agents can keep longer memory notes in a repo, and Work memory can point at them. This expands on the Optional: GitHub notes section of Work memory (Lab) — read that first if you haven't already.

ℹ️ Admin-only to connect. Any member can cite an already-connected repo from their agent; only an Admin can add or remove a GitHub connection itself.

What this buys you

A Work memory's summary always lives in Pulse. But some things — a design write-up, a long investigation, the reasoning behind a tricky fix — don't fit in a sentence or two. Connecting GitHub lets an agent keep that longer note as a Markdown file in your own repo, and cite it from the memory as a pointer: repo, file path, and exact commit. Pulse checks the file is really there at that commit and shows a verified badge — but never reads, copies, or stores the note itself.

Before you start

You need:

• To be a Pulse Admin.
• Work memory switched on for the workspace (Settings → Lab).
• Permission to install a GitHub App on the account or organization whose repo you want to use — or an org owner nearby who can approve it (see step 3).

Step 1 — Settings

Go to Settings → Lab. With Work memory on, a GitHub row appears below Semantic search. If you don't see it at all, this Pulse deployment hasn't set up its GitHub App yet — nothing to connect until it does.

Step 2 — Connect

Click Connect GitHub. Pulse sends you to GitHub's own install page for the Pulse Work Memory App.

• If this is the first time this GitHub account or organization sees the App, GitHub asks you to pick which repositories to share with it (all, or select repos) and confirm the install.
• If the App is already installed on that account (for example, you connected it before and disconnected it in Pulse), GitHub can't show you that install page again — use Connect the existing installation instead. That authorizes you, and Pulse looks up which installations you can access.

Step 3 — If you're not an org owner

Installing a GitHub App on an organization normally needs an owner. If you request the install and you aren't one:

• GitHub queues it as a request to an owner.
• Pulse shows: “Install requested. A GitHub organization owner needs to approve it, then connect again.”