Spool
Connect GitHubConnect

The open source manager that knows whose move it is.

Track your PRs, issues, review requests and mentions across GitHub in one bay, sorted by who owes the next reply.

No token? Browse as a guest: Discover, your plan, GSoC and programs work without one.

Your bay

Sample daySample clock 08:00

Your move

1 on youThey answered. You owe the next word.

Their move

4 on themYou sent it off. Silence is counted in days.
08:00
23:00

LU-881lattice/lattice-ui

Popover loses focus on scroll

Stalled19d quiet

Activity

  1. StalledNobody has replied in 19 daysBefore

Every open thread, wound onto one list. Spool sorts them by who owes the next move, counts the days since anyone spoke, and reads GitHub without ever writing to it.

One list

PRs, issues, review requests and mentions from every repo you touch, wound into one place.

Whose move

Each thread waits on you or on them. That split comes first, before repo, date or label.

Silence, counted

Days since anyone spoke sit on every row. Past your limit a thread is stalled and moves to the top.

A morning in Spool, start to finish.

Scroll to watch someone sign on, work down their bay from the keyboard, answer a review, catch a thread that went quiet and line up the week. Every click is something the app does. Pick a chapter to jump to it.

How a thread becomes a row.

Spool reads each thread from GitHub and works out five things before it gives it a row in your bay. Keep scrolling: the row builds as each one goes by.

Issue

Sample datalattice/lattice-ui #881, as it stands at 08:00 on the sample day.

  1. The threadSpool asks GitHub for every open PR and issue you’re part of: yours, ones assigned to you, review requests, mentions and threads you commented on.
    Searches it runsauthor:youassignee:youreview-requested:youmentions:youcommenter:youFound here: you commented
  2. The callsignThe repo gets a short callsign, unique among your repos, so you can tell them apart without reading the name.
    From the repo’s namelattice/lattice-uiLU
  3. The titleThe title prints as GitHub has it, and the label after it says what kind of thread it is: a PR, an issue or a review.
    As GitHub has itPopover loses focus on scrollIssue
  4. Whose moveThe last comment, review or check run decides whose move it is. You posted a repro here, so the move is theirs.
    The last wordYou posted a reproSep 25Their move
  5. The silenceSpool counts whole days since anyone spoke. Past your limit the count turns red and the thread is stalled.
    Days since anyone spokelimit 14d19 days: stalled
  6. That’s one row.Your bay is every thread like it, sorted by whose move it is, with the stalled ones on top.Open the sample board

Every repo gets a callsign.

Each repo you contribute to gets a short code, unique among your repos and the same everywhere it appears. It leads every row, so you can tell repos apart without reading. Pick one to see its record.

Your repos Sample data

quarry-db/quarry

14 pull requests since March 2026. Merges land in about 4.2 days.

  • QR2417Stream rows from cursor in batchesPR
  • QR2380Fix off-by-one in page cache evictionPR
  • QR2344EXPLAIN shows pushed-down filtersPR
  • QR2301Bench harness for joinsPR
  • QR2290Docs: cursor lifetimesPR
  • QR2255Reuse buffers in the CSV readerPR
  • QR2203Typo in error for bad castsPR
  • QR2187Faster COUNT(*) on clustered tablesPR
  • QR2142Make the planner test deterministicPR

A PR in review is a flight in the hold.

Spool keeps track the way a control tower does. Every PR flies under its repo’s callsign and its own number. While it waits for review it circles in the stack; approval clears it, and the merge puts it down on main. Spool never merges anything itself: it notes the landing when GitHub reports it.

Sample data
  1. HoldingIn review
  2. ClearedApproved
  3. FinalMerge queue
  4. LandedMerged
Next to land
QR2417Stream rows from cursor in batchesWaiting on @mara-k to review.PR
Landed

Nothing has landed yet. The bottom of the stack is next.

Every plane is one PR. Its tail carries the kind’s colour, the same as the dot on its row: violet for your PRs, pink for one you reviewed, grey for drafts parked at the stand. The one circling alone, ringed in red, has been stalled for 31 days.

A PR nobody answers isn’t pending. It’s stalled.

Spool counts the days since anyone last spoke on each thread. Past your limit the count turns red and the thread moves to the Stalled group at the top, with who had the last word. Drag the limit and watch the line move down the list.

14days3 of 6 stalled

Stalled

3 stalledQuiet 14 days or more
  • QR2398Vectorised hash joinLast word: You, Sep 12PR31d
  • LU860Virtualised Combobox listLast word: You, Sep 21PR22d
  • HR5051Retry budget per hostLast word: @ilya, Sep 26: will look next weekPR17d

Their move

3 waitingStill inside your limit
  • MS1102ESM-only build outputLast word: @ana-r, Oct 4PR9d
  • FR296Docs: closures chapterLast word: You, Oct 8PR5d
  • VL612Parallel image decodeLast word: @tomasz, Oct 11PR2d

Sample data3 of 6 threads are past the limit and sit at the top of your bay.

Beyond your threads. Fresh repos in the topics you follow, the deadlines open source plans around, and Google Summer of Code, stop by stop. All of it live.

Fresh repos in the topics you follow.

Spool searches GitHub for repos created in the last five months in your topics and ranks them by stars, so you find projects while they’re still small. These strips are live: pick up to three topics and it searches again.

Your topics2 of 3 picked

Deadlines and launches, on one schedule.

The dates open source people plan around: Y Combinator’s application deadline, Hacktoberfest and each Google Summer of Code milestone, counted down from today, plus what just launched on Product Hunt. All of it is live and refreshed every few hours.

LiveFetched Nov 16 at 17:21 UTC from the sources linked on each strip.

Google Summer of Code 2026, stop by stop.

The whole season on one line, drawn up to today as you scroll. Pick a stop for its date, set your project size to place your evaluations on the line, and filter this year’s 183 organisations by the tech you already know.

NowPhase: ended
Program site
GS2026Program Announce DateGoogle announces this year’s program and its timeline.Coming upDec 3, 2025Date not knowndays

LiveFrom the GSoC program site, fetched Nov 16 at 17:21 UTC.

Your token stays on this machine.

Spool reads GitHub with a personal access token you paste once. It’s kept in this browser’s local storage and sent only to api.github.com. Spool never posts, comments, or changes anything on GitHub. The token is optional: without one you can browse as a guest, and what you save carries over when you sign on.

A classic token with no scopes reads public repos. Tick repo if you want private ones in your bay too. Fine-grained tokens with public read access work as well. Create one on GitHub.

Controller
not signed on
Reads from
api.github.com
Token kept in
this browser
Writes to GitHub
nothing
StatusStatus: waiting