A personal dashboard combining a TUI + Claude Code session launcher that helps me observe and improve all my software and deployments.
active 2026-04-16 → 2026-06-21 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 67 days from 2026-04-16 to 2026-06-21. Pushes: 109 total, peak 7 in a day. Pull requests: 5 total, peak 1 in a day. Issues: 85 total, peak 15 in a day. Comments: 22 total, peak 5 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
Recent activity
Latest issues, pull requests and releases
- Issue#273ooloth2026-06-21 02:45add_comment inserts comment and updates task timestamp in separate SQL calls with no transaction
- Issue#304ooloth2026-06-14 00:03Fold issue-origin tasks to done when their ticket closes
- Issue comment#58ooloth2026-06-11 05:12ui/tui/README.md: Navigation section documents nonexistent Home screen
- Issue#300ooloth2026-06-09 06:21TUI holds a `rusqlite::Connection` in `run_loop` and calls `store::*` directly, bypassing `workflows`
- Issue#300ooloth2026-06-09 06:21TUI holds a `rusqlite::Connection` in `run_loop` and calls `store::*` directly, bypassing `workflows`
- Issue comment#290ooloth2026-06-08 02:25Typed task↔signal origin so a task knows the artifact it produced
- Issue#267ooloth2026-06-06 04:53TUI background dispatch: claim ready tasks and spawn Claude Code agents
- Issue comment#279ooloth2026-06-06 00:31Task dispatch S1: 30s TUI tick atomically claims oldest ready task and spawns agent session
- Issue comment#282ooloth2026-06-05 18:37Move hub.db from ~/Library/Application Support/hub/ to ~/.hub/hub.db
- Issue#284ooloth2026-06-05 17:44TUI source organized by visual concept rather than technical layer
- Issue comment#268ooloth2026-06-05 03:03TUI task queue: create tasks, view backlog/ready in unified list, approve/reject in-review tasks
- Issue comment#268ooloth2026-06-05 02:59TUI task queue: create tasks, view backlog/ready in unified list, approve/reject in-review tasks
- Issue#261ooloth2026-06-03 04:54stream pane: fix text wrapping, auto-scroll, and tool result display
- Issue#251ooloth2026-06-02 06:17TUI calls clients::github directly, bypassing the workflows layer
- Issue#245ooloth2026-06-01 06:24Redact authenticated git clone URL from stderr before forwarding in error messages
- Issue#245ooloth2026-06-01 06:24Redact authenticated git clone URL from stderr before forwarding in error messages
- Issue#245ooloth2026-06-01 06:24Redact authenticated git clone URL from stderr before forwarding in error messages
- Issue#240ooloth2026-05-31 01:32PrSplit: make detail pane focusable with vim-motion navigation and text selection
- Issue comment#56ooloth2026-05-31 00:17Support multiple concurrent hub-tui sessions
- Issue#238ooloth2026-05-30 07:21No TUI keypress to launch agent on `status:ready-for-agent` issues
- Issue#238ooloth2026-05-30 07:21No TUI keypress to launch agent on `status:ready-for-agent` issues
- Issue#236ooloth2026-05-30 06:15github.rs: get_failed_job and get_first_error_annotation silently drop fetch errors via .ok()?
- Issue#231ooloth2026-05-28 07:14Dismiss rollback leaves orphaned comment when close fails after comment is posted
- Issue#231ooloth2026-05-28 07:14Dismiss rollback leaves orphaned comment when close fails after comment is posted
- Issue#231ooloth2026-05-28 07:14Dismiss rollback leaves orphaned comment when close fails after comment is posted
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.