Hmm...https://youtu.be/QsgLS8mSlVs?si=vrwkAXlKer2ColVf

Doesn't exist? Wow you'd better tell VTT to stop their testing then.

Nice. It would be great if it could be used with something like Openrouter BYOK, to give more modern flexibility and costs.

Nice idea. I added it now and it's on the latest VSCode extension and also the Github repository (you can add any API key even OpenAI, Anthropic etc, not just OpenRouter) I also added tons of other things like live test updates, copy buttons on all test cards and issue cards (so you can just copy and paste to claude code to fix the given issue) and also a QA report card which is emitted as the final summary of a test which shows you everything that was tested at one place (no need to scroll up) and allows you to even export it as a PDF (all tests performed / their outcome and all issues found) Let me know if there is anything else

Awesome, I'll definitely take a look asap.

Totally fair and balanced though. /s

I think the problem is there are so many different aspects of this thing we call AI that it's hard to pin down any particular use case. For some users it's brilliant because if you're doing something like marketing imagery etc it can dramatically reduce costs, especially if you're using on premise models on your own hardware without touching the cloud.

But for other uses, i.e. companies who've just thrown AI money at the wall, probably using chatGPT, they wonder why they're not getting the return on investment they were promised. It's all a bit confused at the moment. Rather like the beginning of the internet days were.

Will this work with an openrouter key?

yes Open Router is an option in the onboarding process and in the settings. try it out, and let me know how it goes :D

OpenClaw config needs cleanup Picnic stopped before restart because C:\Users\User\.picnic\openclaw.json contains keys OpenClaw does not accept.

Unsupported keys error: too many arguments for 'config'. Expected 0 arguments but got 1. What is safe to edit Only documented OpenClaw schema fields should live in openclaw.json. Picnic metadata or experiments should go in separate files. Recommended fix Remove unsupported keys, then retry. If you need Picnic-specific metadata, store it outside openclaw.json.

Thanks, dude. Yeah, I'm aware of the bug. We're fixing it right now. The next update should be in about six to eight hours

I'm not having to go at you specifically, but take a guess at how many openclaw / agentic system installations I've done recently which have worked perfectly out of the box. Yep. 0%. Interesting, isn't it?

xD no i get it im with you. We started Picnic out of frustration with the others haha

Looks good. Strange unmemorable name though?

Another classic from the master.

I think people don't understand what shareware is any more.

That's actually quite clever. I guess battery life will be the issue. But nice to see something like this as open source.