Leaving the Agent Running Overnight Is the Real Benchmark
At 1 a.m. in Nakameguro, Yuki typed one sentence instead of a list. Not "rename this function, then update the imports, then run the tests, then fix whatever breaks" — just a single goal, the way you'd leave a note for a housesitter instead of a shift schedule, and closed the laptop lid on it.
The habit came from a note Google's own engineering team published this week about running a coding agent, unattended, against a 200,000-line codebase overnight. The trick that caught her eye wasn't the model, it was the mechanism underneath it: a small manifest file of skills the agent reads once at the start of a session instead of re-reading the whole project tree every time it takes a turn, plus a mode that holds one stated goal steady across hundreds of tool calls instead of forgetting it by call forty. Google reported the session-prep overhead cut by 40 percent and cold imports 21 percent faster. Translated out of engineering: the agent stopped re-chopping the same vegetables before every dish.
She didn't have 200,000 lines to test it on. She had a side project — a small scraper she'd half-abandoned in September — and one real goal: make it survive a schema change on the site it reads. She wrote the skills file herself, four short entries, the kind of thing you'd hand a new hire on their first day instead of explaining from scratch each morning. Then she went to bed, which for an engineer who ships something every night is its own small act of discipline.
The diff was waiting when she woke up. Not clean — she doesn't trust clean, clean usually means something was skipped — but legible: three files touched, one new test, a commit message that correctly guessed why the old selector had broken. What she was actually testing wasn't the model. It was whether she'd written a goal clear enough to survive eight hours without her. That's a harder thing to get right than any prompt, and nobody puts it in the release notes.
The terminal was still open when she sat back down, cursor blinking in the empty room the way it had been blinking at 1 a.m., as if nothing had happened to it at all — except that, somewhere in the dark, something had.
On the wire this week
- Optimizing a 200,000-line Python codebase overnight with Gemini 4… | Accept All Google Developers Blog
Yuki Halvorsen was born in Sapporo to a Norwegian father and a Japanese mother, wrote her first program on a school computer that took ten seconds to draw a circle, and spent eight years as an engineer in Stockholm before Tokyo pulled her back. She still ships something small every night, believes the only honest review of a model is the thing you built with it, and writes Accept All from a desk in Nakameguro where the terminal is always open.