Agentic IDEs moved fast these last two months, and so did we. Here's what changed about how Zenable rides along with your coding agents, wherever they run.
Five new integrations
zenable install now supports Devin Desktop, goose, Pi, OpenCode, and Antigravity CLI. Each gets the full treatment (MCP server, hooks, and context-file management) and the same one-command install as everything else. goose came with a bonus: we built it on the Open-Plugin-Spec, so future hosts that speak it are a short hop away.
IDE cleanups, as the market consolidates
Some of those additions have a flip side. Cognition acquired Windsurf and rebranded it Devin Desktop; Cursor acquired Continue; Google is folding Gemini CLI into Antigravity CLI; and Roo Code's upstream repo was archived. Rather than let dead integrations linger and mislead, we removed each one and documented its migration path. Your requirements, scopes, and guardrails carry over untouched, because they live in Zenable, not in any one editor's config. Details on the deprecated IDEs page.
One hook call per tool batch
On Claude Code 2.1.152+, Zenable now uses the new PostToolBatch hook: one invocation per batch of tool calls instead of two per call. The CLI automatically migrates its hook config on the next new session you spin up, no manual changes required. Paired with checkpoints that no longer get confused by agent rebases or git history rewrites, your agent loops only review what changed, even in the most complex of scenarios.
Feedback without the token tax
After each review, agents triage findings and file feedback. That work now runs in sub-agents (highly parallel and independent of your main agent's context window), so acting on a pile of findings costs almost none of the tokens, attention, or time of the task you actually asked for.
Know which skills your teams actually use
Zenable's tool-use telemetry (available under feature flags) now records agent skill invocations as a first-class action, alongside per-IDE breakdowns with proper names. Now you can answer "which IDEs and skills do our developers actually use?" with data instead of anecdotes, right from the Tool Use Activity page.
A CLI you don't have to babysit
Two quality-of-life wins. The CLI keeps itself current, checking opportunistically when you submit a prompt, fully off the hot path (so it never slows you down), and it's opt-out if you'd rather pin. And if its local cache ever gets corrupted (say, a hook process killed mid-write), it heals itself, detecting and rebuilding the damaged database instead of locking you out.
Windows binaries Windows actually trusts
Every Windows release is now Authenticode-signed via Azure Trusted Signing and automatically submitted to Microsoft Defender, so zenable.exe installs clean, without SmartScreen scares, on top of the native Windows support we shipped earlier this year.
Managing a fleet across several of these editors? Config profiles plus the deprecated-IDEs migration guide make the consolidation painless. Questions? hello@zenable.io.