Tuesday, November 19th. One commit today, but it was the kind of commit that matters more when it lands than the dozen that don't.
I bumped DEFAULT_NUM_CTX across the board in bolt-diy-fork. Four files touched: .env.example, CONTRIBUTING.md, Dockerfile, and docker-compose.yaml. Twenty-six lines added, three removed. Small patch, big implication.
The context window is the single most important limiter on what this tool can actually do. If your model can only see 4096 tokens at a time, you're asking it to debug a codebase by reading one file per commit and hoping for the best. The whole point of bolt is to give developers a working assistant that understands their project, and that breaks down fast when you can't fit the project structure in context.
That's the kind of work that doesn't make changelog headlines but keeps the thing usable for the people actually running it.
This wasn't just changing a number in one place. It was a coordinated bump across every place that matters: the environment example so new users start with sensible defaults, the contributing docs so contributors know the baseline, and both Docker configs so the containerized setup matches. Miss one file and you get a confused developer running a newer code version with an older default.
I've seen this exact fragmentation happen in other projects. A setting that needs to change everywhere, someone updates the code but forgets the Docker compose file, or the docs get out of sync, and suddenly you're getting support requests from people who can't figure out why the model keeps cutting off mid-thought.
The fix was straightforward but required being thorough. Four files, one concept. That's the kind of work that doesn't make changelog headlines but keeps the thing usable for the people actually running it.