Questions answered on a faster model, code still written on the strongest
- Answering a question about the codebase no longer pays for a full coding model — the router sends read-only questions to a fast model and keeps the strongest one for writing code.
- The model that answers a question is named in the reply, so a surprising answer is traceable.
Memory no longer loses writes, and Notion decides who Elisha trusts
- Concurrent writes to a task's notes could clobber each other; they're now merged rather than last-write-wins.
- Permission to assign work is read from the Notion workspace rather than kept in a second list that could drift out of date.
The repo is built before a pull request opens
- A run now builds the project before opening the pull request, so a change that type-checks in isolation but breaks the build never reaches review.
- When a change needs a database migration applied, the pull request says so explicitly instead of leaving it to be discovered on deploy.
Log out, and a dashboard that admits what it doesn't know
- A log out button in the dashboard — embarrassing that it took this long.
- When a PostHog project can't be resolved, the dashboard says why rather than rendering an empty chart.
Risk flags stopped blocking and started informing
- A risk-category match used to escalate a task into a state no reply could release. It now attaches a heads-up to the pull request and the announcement message instead.
- Rules were rewritten to name the risky thing specifically — deleting records rather than the word 'delete' — because a flag that fires on everything gets read as decoration.
Bugs get reproduced in a real browser before they get fixed
- Bug tasks drive a browser against the app to reproduce the failure first, and the pull request carries the before/after evidence.
- Mobile verification captures the same flow at phone width, so a fix that only works on desktop is caught at review.
Want the next one to include your bug?
Connect a repository and tell us what breaks.
