vibehacker
News
Reticle Docs ·

Reticle lets coding agents prove a change works inside your running app, and won't round "couldn't tell" up to a pass

A dev-only SDK, stripped from production builds, instruments your running web, Electron, or Tauri app's DOM, network, routing, console, and state (Redux, Zustand, TanStack Query, Pinia) and exposes it over MCP, so Claude Code, Cursor, Codex, or Copilot can act and get back a yes, no, or unknown verdict with the evidence and the file:line to fix. It runs over a localhost-only bridge, needs Node 20.11+, starts with npx @reticlehq/server init (not npx reticle, which is someone else's package), and sends anonymous usage counts unless you opt out (Show HN).

Read at docs.reticle.sh

More news

View all

GitHub's new package firewall screens npm installs by coding agents and CI runners before they hit your machine

Now in free public preview for GitHub Enterprise Cloud, it sits between coding agents or Actions runners and the upstream registry, checking metadata requests and downloads against admin policy (a configurable cooldown for new versions, Advisory Database malware and vulnerability alerts, attestation downgrades), with an exception request if something is wrongly blocked. It only covers npm for now, each agent or host has to be pointed at the firewall, and it will move to metered billing at GA…

GitHub Changelog

Microsoft will spot Claude Code, Codex, and Copilot on work machines and give each agent its own scoped identity

Microsoft's security stack now discovers 60 kinds of local agents (35 newly added), registers them under their own Entra Agent ID instead of the user's, and is introducing Dynamic Permissions that start an agent with no access and grant only task scoped, time bound rights. New Dynamic Agent Risk and Conditional Access can then block writes, narrow reachable resources, or stop an agent mid task if it hits a prompt injection, though Microsoft gives no rollout or licensing details yet…

Microsoft Security Blog

OpenCode 2.1 adds Windows persistent terminals and todo lists, but breaks plugin and SDK contracts

The Oct 20 release brings persistent PTYs to Windows x64 and ARM64, an opt in todowrite task list via { "experimental": { "todo": true } } , TUI and plugin commands that can outlive Bun's five minute fetch deadline, restored session archiving, editable saved permissions, and compaction that summarizes the whole conversation and kicks in earlier. Plugin, SDK, and HTTP message/event integrations must adopt renamed fields (provider replay data is now native ), though existing sessions and credentials still load with no database migration…

OpenCode Changelog

Mistral Vibe 3.0.1 lets admins ban YOLO mode and makes headless runs wait for, and price, their subagents

Released Oct 20, a day after 3.0.0, it adds an admin managed enable auto approve = false that hides auto approve agents and ignores yolo , makes vibe p wait for subagents its turn left running and export each one's model, usage, and cost, and adds an experimental vibe run server that runs many headless sessions from one process. It also drops the Python 3.14 requirement 3.0.0 introduced back to 3.12+, and retries answers cut off at the output token limit instead of ending the turn…

GitHub (mistralai/mistral-vibe)

AWS's kiro-trace mines Kiro's own runs for fixes, but only deterministic checks decide what ships

The internal loop finds where Kiro fails or wastes effort, proposes one prompt or tool change at a time, and keeps it only if a code based gate (including a full benchmark run against a re run control) and then a human reviewer accept it; in its first week it opened eight PRs and seven merged, including an 83% cut in redundant file re reads and a compaction fix that raised retention from 0.82 to 0.92. A leaner tool and prompt profile that scored 82.4% vs 77.5% pass@1 on Terminal Bench 2.1 at about a third of the token cost is still under review, and all figures are Amazon's internal experiment deltas…

Kiro Blog

Spotted something we missed? Start a thread.