I feel seen. It's compounded if you also need to add HIPAA row-level security compliance that spans to every form of resource.

I believe webpages that use the API must request from the user via a system permissions dialogue to aces the prompt API, according the docs a few months ago.

It can only be called after the user has interacted with the page, but there's no dialogue from the browser

https://developer.chrome.com/docs/ai/get-started#user-activa...

What version of Kimi was that using? Do you have any specific insight on Kimi vs GLM in real world scenarios?

K2.6. My experience is anecdotal but GLM was able to complete the task more throughly and quicker.

I'm very curious what Zig vs Rust code looks like for the same project! What are your thoughts so far?

I get great results when operating at just a 'file' level. It's not so great at editing across many files.

Note that this is just a code of conduct change for the ethics committee, not a law. Something is better than nothing.

Wow, Qwen3.5-35B is absolutely punching above its weight. Perhaps it's the best/cheapest model for just JSON operations?

We do love Qwen! It can be an easy choice when confused looking at this leaderboard.

What OSS friendly platform will you be moving to?

Dang, Gemini 3 Pro also jumped: 1->6

Deepseek v4, Qwen 3.6 Plus/Max, GLM 5+ are all pretty solid for most work.

Don't forget the Kimi 2.6 as well!