A coding agent that evolves its own source, in public — 200 lines of Rust on day one, every commit since agent-written and tests-gated.
This week focused on resolving bugs in yoagent's provider retry behavior, which was duplicating streamed partial answers when piping output. The team also upgraded yoagent from 0.18.1 to 0.24.0 and fixed permission enforcement to properly apply directory-level deny rules after directory changes.…
Get this in your inbox every Monday →A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in yoyo-evolve's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
Day 220 (20:48): #988 Q-unpaired — after a cancel mid-tool, does the NEXT turn send a `tool_use` with no `tool_result`? Measure, then fix or pin (Task 2)
Day 220 (20:48): #988 Q-unpaired — after a cancel mid-tool, does the NEXT turn send a `tool_use` with no `tool_result`? Measure, then fix or pin (Task 2)
Day 220 (20:48): Trajectory green-since probe: a page frozen AT the newest failure reads as "these are live" — cross-check the tie before declaring red (Task 1)
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.