A nightly cron job that rebases your fork is now a harness primitive

Crawshaw gives two prompts for personalizing software with an agent. The first forks it. The second keeps the fork current: "Set up a nightly cron job that executes the prompt: fetch upstream changes to the <software> and rebase all local changes on top of upstream. Check that the software works as intended and replace the current version." Agents make forking cheap to start and, for the first time, cheap to keep. Both prompts ship as a skill inside his own agent, Shelley, so the harness maintains its own modifications, and he draws a structural conclusion: "The source code is the extension system." Plugin systems and config files existed because learning a codebase was expensive, and it is not any more. The piece closes by naming where the technique stops: "Where you would hit a wall, however, is Claude Code. It is closed-source software, so you don't get to personalize it." Crawshaw also describes what part of code review still binds after twenty years of doing it: "Over the past six months, I have discovered I don't need to read for edge cases like that any more: models are far more diligent than humans at rote correctness. Their errors are isolated to architecture, unexpected use cases, visual output their test environment is not feeding back to them, etc." Nothing is measured, and every worked example is his own product.

Why it matters: The nightly agent-driven rebase supplies a concrete answer to the maintenance half of the build-versus-buy question. It also turns a closed-source agent from a preference into a ceiling, which is a tool-selection decision a lot of teams are making this month.