Example z.ai/blog/glm-4.7
These percentages are so abstract that is hard to evaluate is this better in everyday usage than SOTA.

If you automate this with Linear and Slack. You can shorten time to PR dramatically. Most importantly you don’t commit into any additional AI subscriptions while keeping control of the whole execution env, what MCPs can be used, what agent can and can’t do.

Despite all this, we got a working plugin! WebSocket-powered, CRDT-backed, and even supporting browser editors.

I’ll share the code once it’s cleaned up and a few bugs are ironed out. Stay tuned! ⚡️ #neovim #rustlang #lua #crdt #hacking

3️⃣ Rust async gotchas? As Rust newcomers (more async Rust newcomers), we underestimated how much time we'd spend debugging errors like "cannot move XYZ because Foo doesn't implement Send", where Foo was some deeply nested type. On top of that, most of LLMs didn't know how to fix these issues too.

2️⃣ Nvim API quirks? Turns out, there's no way to track byte-level changes—only full-line diffs on remote API. Not ideal for real-time collaboration. We had to create a custom event type and send it via a socket from Lua to Rust.

1️⃣ Lua ↔ Rust communication? After some trial and error, we ended up spawning a separate process and using NeoVim’s remote API for better isolation. We thought about using nvim-oxi or mlua, but after a few tries to set up it correctly, we backtracked to bulletproof rmp.

We used Lua + Rust, with CRDT (via the yrs library) under the hood. Nice API, solid Node & Rust support. But, of course, we hit some roadblocks:

Joking if not obvious :D

Link’s broken

Kindly submitting team application

Ok, this seems related github.com/microsoft/Ty... 🤔

Check Avante (my personal pick) or Code companion