Skip to content

agent-fox is an autonomous coding-agent orchestrator built exclusively for Claude.

active 2026-02-172026-08-11 (UTC)

Partial coverage20,510 / 26,266 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-152026-08-13 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
1.3K
Pushes
704
Pull requests
19
Issues
165
Stars
2
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 176 days from 2026-02-17 to 2026-08-11. Pushes: 704 total, peak 28 in a day. Pull requests: 19 total, peak 7 in a day. Issues: 165 total, peak 17 in a day. Comments: 101 total, peak 18 in a day. Stars: 2 total, peak 1 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
mickume98870419100
m13v1001

Recent activity

Latest issues, pull requests and releases

  • Releasemickume2026-07-27 15:16
    v4.2.9
  • Issue#705mickume2026-07-08 12:11
    refactor: extract [backend] config section with unified provider selection for af, nightshift, and spec
  • Issue#669mickume2026-07-03 09:03
    Investigate merge conflict rate in parallel spec execution
  • Releasemickume2026-07-02 14:54
    v4.0.3
  • Issue#667mickume2026-07-02 12:55
    refactor: simplify local config.toml creation and loading semantics
  • Issue comment#633mickume2026-06-26 05:13
    Change configuration loading
  • Issue comment#623mickume2026-06-26 05:11
    enhancement: supersede resolved drift findings as task groups complete
  • Issue comment#623mickume2026-06-26 02:02
    enhancement: supersede resolved drift findings as task groups complete
  • Issue comment#623mickume2026-06-26 01:26
    enhancement: supersede resolved drift findings as task groups complete
  • Issue comment#623mickume2026-06-26 00:36
    enhancement: supersede resolved drift findings as task groups complete
  • Issue comment#623mickume2026-06-26 00:08
    enhancement: supersede resolved drift findings as task groups complete
  • Issue#625mickume2026-06-25 06:33
    improve spec creation
  • Issue#625mickume2026-06-25 06:33
    improve spec creation
  • Issue#616mickume2026-06-25 04:23
    bug: worktree setup fails on startup when stale directories exist despite preflight prune
  • Issue#612mickume2026-06-24 06:48
    Limit test suite runs per coder session to prevent fix-test-fix loops
  • Issue comment#564mickume2026-06-14 04:08
    Session summaries should be stored in the database
  • Issue comment#595mickume2026-05-20 11:09
    Error while loading shared libraries in container image
  • Issue#597mickume2026-05-20 10:14
    Deprecation warning from default config.toml
  • Pull request#596mickume2026-05-13 00:11
  • Issue#583mickume2026-04-30 09:13
    Exception details leaked to GitHub issue comments in fix_pipeline.py
  • Issue#587mickume2026-04-30 08:44
    shutil.rmtree follows symlinks during worktree cleanup
  • Issue comment#581mickume2026-04-30 08:36
    Incomplete SSRF address checks missing reserved/multicast/unspecified ranges
  • Issue#585mickume2026-04-30 08:14
    Path traversal risk in profile loading due to unsanitized archetype/mode parameters
  • Issue#583mickume2026-04-30 08:14
    Exception details leaked to GitHub issue comments in fix_pipeline.py
  • Issue#583mickume2026-04-30 08:14
    Exception details leaked to GitHub issue comments in fix_pipeline.py

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