Trend

Coding-agent work is concentrating on operator control and guardrails

Day · 2026-06-26 · Software Intelligence

This day’s corpus is small and practical. Workbench focuses on running several coding agents without losing state. Ratchets focuses on low-cost rule checks that stop agents from adding unwanted patterns.

Parallel agent workbenches

Workbench packages multi-agent coding into a full-screen terminal user interface (TUI). Each workspace can hold an agent pane, shell panes, open files, and a live git diff. The design targets a common operator problem: running several agents while still seeing files, changes, and sessions in one place.

The strongest concrete detail is persistence. Agent and terminal panes run inside a private tmux server, so restarting the UI can reattach to live processes. The tool claims support for Claude Code, Gemini, Goose, OpenCode, and Cursor, but the corpus gives no task benchmark, latency result, or user study.

Rule ratchets for agent-written code

Ratchets treats code-style and safety rules as counters that block new instances of forbidden patterns while tolerating existing debt. That fits agent workflows where a model may choose a quick suppression, such as # pyrefly: ignore, without enough project context.

Ratchets v0.4.0 replaces Rust’s regex crate with Resharp. The stated reason was lookaround support for rules that work better as text patterns, especially comment-style rules. On the Sculptor codebase, the author reports about a 15% speed gain after the regex engine change, with no absolute runtime or repeated-run details.

NewerCoding agents need safer senses and stricter cost accountingOlderRobot VLA papers are converging on rollout-grounded reliability