Skip to content

The AI coding agent built for the terminal.

active 2025-10-082026-05-11 (UTC)

Partial coverage15,136 / 18,552 hourly files (82%) · 2 absent upstream · 3,415 failed, retryable2024-06-292026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
572
Pushes
146
Pull requests
66
Issues
162
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 216 days from 2025-10-08 to 2026-05-11. Pushes: 146 total, peak 13 in a day. Pull requests: 66 total, peak 7 in a day. Issues: 162 total, peak 24 in a day. Comments: 69 total, peak 14 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
randomm4341466065
github-actions[bot]10064

Recent activity

Latest issues, pull requests and releases

  • Issue#410randomm2026-04-12 17:06
    Bug: LLM stall timeout fires on interactive PM sessions waiting for human input
  • Pull request#411randomm2026-04-12 17:06
  • Issue#408randomm2026-04-10 21:29
    fix: restore external plugin loading in Plugin.init()
  • Issue comment#405randomm2026-04-09 20:41
    Bug: Composer agent has no tool permissions — cannot read codebase to decompose issues
  • Issue#382randomm2026-04-08 13:12
    fix(taskctl): Pulse not detecting commits in worktrees causing adversarial never to spawn
  • Issue#383randomm2026-04-08 13:12
    fix(taskctl): developer-pipeline starts in main worktree instead of assigned worktree
  • Issue#381randomm2026-04-08 13:12
    feat(taskctl): make start command resilient to existing branches
  • Pull request#402randomm2026-04-08 10:38
  • Issue#398randomm2026-04-08 10:04
    EPIC: Subagent LLM stall detection and visibility
  • Pull request#397randomm2026-04-08 08:03
  • Pull request#392randomm2026-04-07 19:37
  • Issue comment#388randomm2026-04-07 17:11
    Bug: taskctl pipeline - no PM escalation after 3 adversarial rejections causes infinite loop
  • Issue#384randomm2026-04-06 09:48
    fix(taskctl): adversarial-developer feedback loop loses context between rounds, causing rewrite loops
  • Pull request#385randomm2026-04-06 09:48
  • Issue comment#383randomm2026-04-05 20:29
    fix(taskctl): developer-pipeline starts in main worktree instead of assigned worktree
  • Issue#383randomm2026-04-05 20:25
    fix(taskctl): developer-pipeline starts in main worktree instead of assigned worktree
  • Issue comment#381randomm2026-04-05 20:23
    feat(taskctl): make start command resilient to existing branches
  • Issue#382randomm2026-04-05 20:20
    fix(taskctl): Pulse not detecting commits in worktrees causing adversarial never to spawn
  • Pull request#380randomm2026-04-05 19:52
  • Issue#379randomm2026-04-05 19:44
    fix(session): use session.directory instead of Instance.directory for path.cwd in messages
  • Issue#376randomm2026-04-05 10:04
    feat(taskctl): enhance adversarial-pipeline prompt and verdict schema with TESTED_SCENARIOS
  • Pull request#377randomm2026-04-05 10:04
  • Issue#376randomm2026-04-05 09:47
    feat(taskctl): enhance adversarial-pipeline prompt and verdict schema with TESTED_SCENARIOS
  • Issue#376randomm2026-04-05 09:47
    feat(taskctl): enhance adversarial-pipeline prompt and verdict schema with TESTED_SCENARIOS
  • Issue#218randomm2026-04-04 19:09
    feat(tool-use-fix): cherry-pick upstream PR #8497 — fix dangling tool_use blocks on abort/crash

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.