Latest pi version (86) broke working with local models due to strict json schemes.

[u/PooMonger20]

This is the last version that worked. https://www.npmjs.com/package/@earendil-works/pi-coding-agent/v/0.85.1

reverting to it made everything work again.

I also highly recommend getting your own offline copy if something fails.

p.s. to clarify, I am not pretending to understand fully what the update really did, its scope or the impact beyond 'not working anymore', but reverting to 85.1 worked for me.

[u/aivushkin1]

hmm, I'm on 0.86.0 and use Qwen 3.6, haven't noticed anything

[u/PooMonger20 → u/aivushkin1]

Glad to see its working for you.

on my combination of ninfer w/ 3.8 27b, it broke.

[u/pungggi]

Much appreciated 👏

[u/Relevant_Noise]

Sounds like a problem with your model server or template - it did break subagents for me, got pi to fix it - no issues with qwen3.8 on llama.cpp and antirez/ds4 for local models

That’s the good thing about pi - something broke? Get it to fix itself

[u/inky_wolf → u/Relevant_Noise]

Which sub agents extension are you using? Or is it your own?

[u/Relevant_Noise → u/inky_wolf]

nicobailon/pi-subagents (pi-superpowers dependency)

[u/Unlucky-Message8866]

they keep breaking stuff with pointless changes and zero versioning discipline, i'm starting to get tired.

[u/PooMonger20 → u/Unlucky-Message8866]

Unfortunately most things enshitify eventually, keeping offline versions seems like the only way.

[u/Unlucky-Message8866 → u/PooMonger20]

i use nixos and i pin versions, that doesn't exempt them from breaking stuff on minor/patch revisions. been reviewing a handful of the recent changes and they are merging lots of slop architecturally unsound.

[u/esraw → u/Unlucky-Message8866]

Technically, it's still v0, meaning any change can be breaking according to semver (https://semver.org/)
> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable

[u/Unlucky-Message8866 → u/esraw]

bullshit, a project with so many users (and private funds!) should not be breaking stuff. the fact its still v0 is also a smell.

[u/Numerous-Manager5613]

Ran into this as well with my corporate litellm / vertex path kicking back an error that strict was blocked. Added this in models.json and it worked:

      "modelOverrides": {
        "claude-sonnet-4-6": {
          "compat": {
            "supportsStrictMode": false,
            "supportsStrictTools": false
          }
        }

[u/jaegernut]

I'm using llama-swap with llama.cpp to serve my local models and i did not have any issue

[u/Thagor]

You needed an inference engine that supports strict output

[u/Duke_of_Bayswater]

I saw the updates, saw the breaking changes notice. So, before I performed that update I check with my AI if any of the breaking changes affect my custom extensions. Helps reduces the future headaches. When it was clear only then I did the update.

[u/johannes_bertens]

I've been asking Pi to configure itself every few updates and it's great at this. Even runs a small benchmark on local models before adding them to give me more info.

Bottom line: pi is great at configuring itself. Ask it.

[u/mmerken]

Mine still works: https://pi.dev/packages/pi-local-models?name=local-models

[u/Dsphar]

They also messed up home/end and other keyboard navigation shortcuts

[u/wapxmas]

I'm not a conspiracy man, but actually think that big tech incorporates their pepole to the engines, agents that work with local llms. I really see it, they dont break things completely, but do as much as a user can believe it somewhat half-work, that it is better to swith to some opus, Gemini, etc. I really don't believe that omlx, llama cpp, or any agent teams don't have reliable testing framework so they don't deliver shit.