SELECT 1
Entry 009Mon 2026.10.19
One launch a day. Picked, run, explained.

← View the entry

Entry 009 ProgressSphinx: explaining the changed code before it can be pushed

exit 0Ran itIt works. The push stayed blocked until the answer passed, and then the same push continued.
  1. Day 3Active
  2. Day 7Active
  3. Day 15Upcoming
  4. Day 30Upcoming
  5. Day 90Upcoming
  6. Day 180Upcoming
  7. Day 365Upcoming

Latest check Day 7, Sun 2026.10.25

Commits since launch
32 → 64
Stars
99 → 374
Last commit
2026.10.24

Numbers by checkpoint

CheckpointCheckedStateCommits since launchStarsReleasesContributorsLast commit
Day 1Mon 2026.10.193299022026.10.18
Day 3Wed 2026.10.21Active45206032026.10.19
Day 7Sun 2026.10.25Active64374062026.10.24
Day 15Due Mon 2026.11.02Upcoming
Day 30Due Tue 2026.11.17Upcoming
Day 90Due Sat 2027.01.16Upcoming
Day 180Due Fri 2027.04.16Upcoming
Day 365Due Mon 2027.10.18Upcoming

What changed

Day 7 Sun 2026.10.25

  • When a commit pushed to main passes its checks, it is released as the next patch version (0.1.15).
  • When a pending Git operation passes its check, Sphinx asks the user whether to continue.
  • Transient OpenRouter errors are retried with backoff, and ungraded answers are kept.

Day 3 Wed 2026.10.21

  • Trivial changes pass without questions.
  • If Sphinx cannot open a browser, it asks the questions in the terminal.
  • The user can choose whether questions cover the design or the implementation details. The default mixes both.
  • Coding agents can set up a repository with init --suggest and --apply. An agent’s proposal cannot switch the checks off.
  • When API requests hit a rate limit, Sphinx offers to continue the review on the user’s Claude Code or Codex plan.