There are upcoming benchmarks aimed at measuring the ability to work with brownfield tasks. (Of course, benchmarks can be gamed, but they are still better than unrealistic toy tasks that earlier generations of benchmarks used. Frontier labs are yet to use them in their tech reports or marketing material, though.:-)
I've found [Plannotator]( https://github.com/backnotprop/plannotator) useful for this. It opens the plan on a minimal web page so I can highlight and add comments. This is then passed back to Claude code. Works well enough for now. But ideally this should be natively implemented in cc.
Using LM-Studio as the frontend and Playwright-powered MCP tools for browser access. I've had success with one such MCP: https://github.com/instavm/coderunner It has a tool called navigate_and_get_all_visible_text, for example.
I wish this was supported by default in the Kindle browser. I wonder if there was a way to make it an extension or a wrapper and make it available in eink device browsers. But it seems that even this blog post page is not supported in the Kindle browser. (I don't see the eink mode icon.)
The requirements for me are simple, primarily to make consuming web content on my kindle scribe easier.
* Instead of scrolling by finger gestures (which is a pain to watch on slowly-refreshing eink), have two buttons on the side to do page up and down.
* Disable animations
* Ability to increase/decrease font size.
If you have an android based eink device, try einkbro https://github.com/plateaukao/einkbro It supports mapping pageUp/down to touch gestures or physical buttons. You can avoid scrolling that way. I wish I had a way to install on a Kindle too
According to the OSI's open source definition, you can't put restrictions against persons or groups or fields of use. In the license, Linux is not restricted in what domain it will be used (good or bad).
* SWE-EVO: Benchmarking Coding Agents in Long-Horizon Software Evolution Scenarios https://arxiv.org/abs/2512.18470 * SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via Continuous Integration https://arxiv.org/abs/2603.03823