> Specifically, all it took to boost Qwen3.8-27B to get 10% more points on SWEbench Pro and Terminal Bench 2.0 with a proxy that has just these basics

Do you have a link/paper for this you could share?

I haven't written one. You can easily replicate it if you wish just based on my comment and a day spent with Claude Code.

In fact that is how I got the idea. There is a 4 month old post on SWEbench github that claimed 20 point boost (beating opus as well) for another small Qwen model when it's traffic was sent via a similar proxy and claude code was used as the harness.

The author didn't post their full code, but he did post all sorts of logs showing which features of his proxy were activated during which run.

I wanted to exclude the harness and validate his claims regarding only the proxy's impact so I reimplemplemented a subset of his features that seemed to give me the biggest "wins" with the smallest amount of work. These are the ones I list in the parent.

It took one afternoon last week plus the runs that took few days.

I saw about 10% better results.

As I mentioned, it is a subset of tasks, not the entire set, but results so far are very encouraging.

Since then I implemented many more features in the proxy (best of N for example), but i haven't had time to measure the impact yet. His proxy also had best of N, but that feature wasn't activated in on the runs he reports.