Hmm, maybe not... just got this back:
"The file was cut off mid-statement in the previous write operation - I need to read what was written and complete it properly."
That's what #pidev was reporting too, so perhaps the issue is with the new version of ollama
Hmm, didn't help for long. Still all kinds of issues with #pidev not being successful with tool calls that have worked in the past no problem,. Models are unchanged. ollama version did change (updated to get a new model), and the pi.dev version updated too.
Luckily, I still have one of my Claude compatible local models and that seems to be working OK.
so apparently you can use a Mistral API key in a coding agent, such as Pi, and have it use your monthly subscription but it is tricky to find.
There is a separate dedicated Vibe API key which is separate from the pay-as-you-go keys.
On the Code Extensions page, click on advanced, and look for "Vibe API Key"
There's probably a billion extensions for the #Pi harness dedicated to keeping the agent tool calls from touching anything outside the working directory...
So here's another one.
It has a global whitelist, and lets you Deny/Allow/Allow Session/Always Allow.
It's got a shitload of tests but I haven't bounced on it enough yet to trust it yet. Gonna be dogfooding it. :P
Reposting from X: Pi is moving to earendil-works GitHub org and the published packages namespace is changing too. Switch your Pi agents. This is a breaking change an new versions do Pi plugins wonβt work with newer Pi releases.
People of https://t.co/oUoqqL9hAp. Today we are: - moving the pi GH repo to earendil-works org - start publishing pi packages under the @earendil-works namespace, instead of @mariozechner for the time being, extensions importing from the @mariozechner will continue to work,
John Gordon π·
Karl Ostendorf
Dr. Fortyseven π₯ ββββ
Jakub Synowiec