CC-Canary: Detect early signs of regressions in Claude Code

The brown m&m trick turns out to have more applications than one would think!

Mind sharing that block? Is it just: "Persona: You are HK-47"?

"we investigated ourselves and found nothing wrong"

I am on the same boat, started to build my extensions and preferences in PI. The community is awesome and helpful. My assumption is the personalization has higher priority than the intelligence gap between opus and gpt or others. At least i wont stop working if claude is down.

i think a lot of us are kind of sitting back and seeing what dark horse rises up. it's such a non-deterministic outputting technology that's still in discovery mode and the resources expenses/constraints are outta control, the companies leading the charge are eating themselves and can't guarantee jack squat. down in the trenches people have built these things up to be critical dependencies in either their day to day life or their work, my eyes are mostly glazing over hearing about how people are using claude to do whatever grand array of things with no oversight. the way we benchmark this shit is all over the map, the goalposts are just teleporting randomly at this point.

my claude usage has drastically dried up as i've personally realized the real bottom of this stuff is always gonna be genuinely learning and becoming excellent at a thing. i think claudes not bad for helping me get through early stages of that process, and for actual work i think claudes great for just ripping out something im too lazy to do, but something i know so well that i can catch him slippin. absolute coinflip on if it's worth the pain, many times now ive said "i shouldve just done this myself".

i've got my fingers crossed for like llm's to reach some sort of proverbial opus 4,5 territory here. even if thats gonna cost me a bit in hardware, that's kind of my personal bench mark for "good enough, i'm unplugging from all this craziness".

one thing is for sure, anthropic needs to stop adding _features_. claude code or vscode extension was their bread and butter reliability that garnered them a lot of goodwill from people who were willing to pay good money for a good service. seeing them launch their design thing just has me rolling my eyes. they're kind of microsoft'ing themselves here by trying to do too much, and they'll end up delivering a lot of subpar services that aren't best-in-class at any one thing. we're already seeing that i think.

IDK how it applies to LLMs but the original meaning was a change in a distribution over time. Like if you had some model based app trained on American English, but slowly more and more American Spanish users adopt your app; training set distribution is drifting away from the actual usage distribution.

In that situation, your model accuracy will look good on holdout sets but underperform in user's hands.

This definition satisfied me: https://universalpaperclips.fandom.com/wiki/Value_Drift

I believe it's businessspeak for "change." Gap is suittongue for "difference."

there are many causes, but it’s a drift in performance

you can drift a tool via the harness in many ways

you can modify the system prompt

you can modify the underlying model powering the harness

you can use different “thinking” levels for different processes in the harness

you can change the entire way a system works via the harness, which could be better or worse, depending on many things

you can introduce anti-anti-slop within the harness to foil attempts from users using patch scripts

you can modify how your tool sends requests to your server depending on many variables

you can handle requests differently, depending on any variable of your choosing, at the server level

you can modify the compute allotment per user depending on many things, from the backend, without telling the user, it’s very easy. you can modify it dynamically depending on your own usage or the user’s cycle. Or their organization’s priority level as a customer. The weekly and daily usage management system is intricate, compute is very finite and must be managed

the user has literally no way to know and you have no legal obligation to tell them, you never made them any legally binding promises

the combination of so many factors that all affect each other means that you can, if you’d want to, create a new clusterfuck of an experience anytime any of these or unknown variables change, it may not even be deliberate, it grows exponentially complex, so you may not even be able to promise a specific standard to your users

drift is not imagined, sure, but admitting to it could expose you to unneeded liability

See the very last section in this doc for how I minimise token usage and track savings, all three plugins co-exist fine: https://github.com/FrankRay78/NetPace/blob/main/docs/agentic...

like the status page of a service provider that goes down when the service goes down. you had one job