to me it does feel equal or better than at least current sonnet. i cobbled another machine with spare parts i had lying around from an old mining rig only to have another 27b instance running, Q4 100k context. I now have two qwen 27b in the lab

I just tried the Q4 with the first task, im using lean-ctx to optimize context inside PI, i wanted to have a local build for security reasons, without calls to remote api's, etc.

I had a sonnet built plan, first thing qwen 3.6 27b did was to correctly question multiple parts of the plan and rework it.

Then started clean in another PI instance , installed rust, and all the shit it needed for the build. Keep in mind that is actively using the lean-ctx while re compiling AND deploying it, at one point it replaced the bineary for the first time and it had a bug. It was trapped because almost ALL calls go through lean-ctx, so i though ok, i have to manually revert the binary, but no, after 10 different tries it found a workaround, fixed, redeployed and everything is working, all by itself 40% token usage in the entire 10 minutes session. Insane. Im grinning like a maniac right now

cita

The lean-ctx middleware is intercepting every command. The broken JS wrapper is poisoned. Let me check how lean-ctx wraps bash commands:

$ echo hello

lean-ctx binary not found. Run: npm rebuild lean-ctx-bin

Command exited with code 127

Compressed 22 ? 22 tokens (0%)

Took 0.4s

Every bash call goes through lean-ctx first, which invokes the broken JS wrapper. I need to restore the JS file. The write tool should work since it doesn't go through bash:

write C:\Program Files\nodejs\node_modules\lean-ctx-bin\bin\lean-ctx.js

#!/usr/bin/env node "use strict";

const { spawnSync } = require("child_process"); const path = require("path");

const IS_WIN = process.platform === "win32"; const BINARY = path.join(__dirname, IS_WIN ? "lean-ctx.exe" : "lean-ctx");

const result = spawnSync(BINARY, process.argv.slice(2), { ... (14 more lines, 24 total, ctrl+o to expand)

JS restored. Let me verify bash works again:

$ echo hello

hello

Compressed 2 ? 2 tokens (0%)

Took 1.5s

Bash restored. Now let me properly replace the binary. Since I can't write to Program Files via sh, I'll modify the JS wrapper to point to the new binary location: