We just shipped Zagens v0.8.5 our open-source desktop agent harness for DeepSeek V4. This release is all about seeing what the agent actually knows, running sessions in parallel without stepping on each other, and recovering when things go wrong.
v0.8.1 is out. If you ve been waiting to run a DeepSeek V4 coding agent outside a browser tab, the headline is: Kernel V3 is now the sole production turn engine, and zagens-tui ships as a first-class full-screen terminal surface on Linux, macOS, and Windows same runtime threads and harness as the desktop app.
What s new
Kernel V3 (event-sourced turn engine) We replaced the legacy imperative turn loop with an append-only KernelEvent log in sessions.db, a LiveTurnMachine planner, and an EffectInterpreter that executes model calls, tool batches, steer injection, and long-horizon hooks. Session resume is log-first; CI verifies turns with golden replay fixtures instead of shadow bakes. Desktop, TUI, and headless CLI all hit the same path no lite terminal fork.
Quick update from the Zagens team. v0.7.4 is out, and the headline for Windows users is native OS-level sandboxing not just a config flag, but real process isolation when agents run shell commands on your machine.
Why this matters
Most desktop agents can run arbitrary commands locally. That s powerful and risky. Zagens has always treated exec policy + approval UI as the baseline. With this release, Windows gets the same class of enforcement macOS already had via Seatbelt: restricted tokens, workspace write boundaries, and (in elevated mode) profile read isolation + outbound network blocking.
