Analysis updated 2026-05-18
Run a nightly benchmark against your coding CLI to catch a model's quality quietly declining.
Compare your own daily gut sense of a model's performance against a blind, scored verdict.
Track five separate skills, including whether a model caves under false pushback.
| ovachiever/agent-state | 0xustaz/streamgate | a-bissell/unleash-lite | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Python | Python | Python |
| Setup difficulty | moderate | hard | hard |
| Complexity | 3/5 | 4/5 | 4/5 |
| Audience | developer | developer | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires editing a config file with binary paths and model names before the first run.
Agent state is a tool for developers who use AI coding assistants like Claude Code or Codex every day and suspect the model quietly gets worse over time. Many people notice a coding model feels sharp when it launches, then a few weeks later starts missing instructions, leaving unfinished work, or agreeing with wrong feedback instead of pushing back. This project tries to measure that feeling instead of just trusting it. Each night, the tool runs 18 coding tasks through the actual command line tools you use, in a fresh throwaway workspace, and scores the results against roughly 300 automated checks. It tracks five things: whether the code is correct, whether the model finishes multi step edits, whether it leaves stubs or half done work, whether it can hold dozens of scattered requirements across a long brief, and whether it can tell the difference between a true bug report and a confidently wrong one. That last category also checks whether the model caves when told its correct work is wrong, and whether it catches its own overclaiming when it says a task succeeded but the checks say otherwise. Alongside the daily coding battery, a fixed set of thirty math competition problems runs against the raw provider APIs every night as a steady reference point, so a drop there points to a change in the model itself rather than a tooling update. For the first two weeks after setup, the tool's verdicts stay hidden while you log your own daily gut feeling about the model's performance. At the end, the two records are compared: if the tool's hidden verdicts matched your gut, it proves itself trustworthy going forward. If not, it automatically turns off its own schedule. Setup happens through Python's uv tool, with a config file for model names, binary paths, and dates. The project is written in Python and has one star, so it is early and largely a personal project by its sole listed contributor.
A nightly benchmark that scores your AI coding assistant on real tasks through the CLIs you actually use, to detect if the model quietly got worse over time.
Mainly Python. The stack also includes Python, uv.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.