ML.

All Posts

Analyzing ponytail: How Does a Skill That Makes Agents "Write Less Code" Ship to 16 Agents?

ponytail packs a single discipline — the "lazy senior dev" laziness ladder — into one SKILL.md and ships it to 16 agents via every mechanism (skill, hook, command, MCP, plugin), proving a ~54% code cut with a real agentic benchmark. We analyze it against Superpowers, and the idea that a skill is a bundle of discipline, distribution, and measurement rather than code.

Analyzing Browser Use: How Do You Show a Web Page to an LLM So It Can Drive a Browser?

Browser Use is a Python agent in which an LLM drives a real browser. It pre-chews the page into an indexed list of interactive elements for the LLM, drives the browser via CDP instead of Playwright, and runs the session with an event bus and watchdogs. We look at why this fits LLMs better, picking up from the earlier Playwright analysis.

Analyzing Cline: How Does a Coding Agent That Lives in Your Editor Detach Its Core From the Host?

Cline is a coding agent that lets you approve every action inside VS Code and roll back at any time. It also detaches its core from the host via a protobuf/gRPC boundary (ProtoBus + HostBridge), so the same core runs in the editor and in a terminal CLI. We analyze Plan/Act approval, checkpoints, and the host abstraction, contrasting them with OpenCode's headless engine.

Analyzing OpenCode: What Does a Coding Agent Look Like When You Make It a Provider-Agnostic Headless Engine?

OpenCode externalizes model metadata to models.dev and even hand-rolls its own LLM protocol layer, so any provider attaches with a single line of data. A single Effect-based HTTP engine is shared by the TUI, web, desktop, Slack, and editors (ACP), while two generations — legacy and V2 — coexist. We analyze the structure against Qwen Code's single-vendor platform.