Unpack both tarballs and compare md5 file by file: 8 packages, 290 files, 8 differences, all of them in package.json. The version number went from alpha to rc, not a line of code moved, but every dependency got bumped, and plugins have to follow.
On Android 16 every app can declare functions like an MCP server. I sent a message from outside my own app with zero screen touches, and dug out the internal|privileged permission gate.
The same screen: a 77 KB screenshot the model has to guess at, versus 4,184 bytes of text that states the structure. I ran both on an emulator, and hit the parts it still cannot do.
JetBrains analyzed 4,782 real IDE sessions: splitting one request into three messages more than doubles cost and barely moves the resolve rate.
The version on npm is not the newest one. You have to pin the version number to get it. Once installed, three plugins were rejected on the spot. Not a bug. An exact-version lock doing its job.
The IDE terminal has a new engine: JediTerm, thirteen years old, steps aside for Ghostty’s core library. The reason is written on the AI agent line. I unpacked the new build and checked.
1,778 lines of documentation, 3,498 lines of validation. The heaviest part of Cloudflare’s open-source audit skill is not finding bugs, it is stopping the agent from inventing them.
I have had memorix attached to my DeepSeek Harness the whole time. Months of use, zero problems.
DeepSeek Harness keeps saying Everything is a Plugin, meaning features are all built as plugins. Version 0.2.1 moved one step further and started managing where plugins come from: rc.1 added an entry that lets users discover and install plugins from custom plugin index sources.
The most common way to make an agent drive software right now is to let it look at screenshots, find buttons, and click coordinates. It works, but it is brittle. Resize a window, move a button a notch, let a page load half a beat slow, and it starts clicking blindly.
Number one. You paste a chunk of logs into your agent client to chase down a problem, and the logs carry a line DEEPSEEK_API_KEY=sk-.... Problem solved, and that line is still sitting in the session history.
You have an agent write some Kotlin. It says it’s done. Now what?