Skip to content

Local-first work coordination for developers and coding agents

active 2026-07-152026-08-16 (UTC)

Complete coverage26,539 / 26,539 hourly files (100%) · 2 absent upstream2023-08-152026-08-24 (UTC)
Events
64
Pushes
33
Pull requests
1
Issues
3
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 33 days from 2026-07-15 to 2026-08-16. Pushes: 33 total, peak 6 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 3 total, peak 2 in a day. Comments: 2 total, peak 2 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
highbyte373310
sonarqubecloud[bot]2002

Recent activity

Latest issues, pull requests and releases

  • Issue#104highbyte2026-08-07 18:15
    Releasing a claim clears the dispatch state by default, silently demoting paused items
  • Issue#105highbyte2026-08-07 18:15
    A paused session with no dispatch state cannot be resumed from any surface
  • Issue comment#106sonarqubecloud[bot]2026-08-07 18:13
    Make every claim release state what happens to the dispatch state
  • Pull request#106highbyte2026-08-07 17:56
  • Issue comment#103sonarqubecloud[bot]2026-08-07 16:40
    Launch a recorded session from paused board cards
  • Issue#41highbyte2026-07-28 15:12
    Add cache path, status, and node-ID clearing commands

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.