Agent Frontier Research
Research notes for operators using coding agents.
Bitter Frontier tracks coding agents, terminal harnesses, model CLIs, runtimes, verification surfaces, and operator workflows. The frontier changes; the loop should compound.
Canonical Digest
Frontier Roll-Up: April 22-May 6, 2026
Published from Goal-weighted canonical rerun for initial frontier roll-up. 6 signals, 5 findings.
Top Signals
Worker-native goals unlock longer horizons.
Codex /goal is a worker-native objective register, not merely a memory feature. It lets a coding worker carry a persistent direction of travel across longer arcs of work.
Worker-native state is becoming a memory layer.
Worker tools are adding native mechanisms for carrying context forward, including recaps, memory patches, skill reports, curator outputs, and resume state.
Authority semantics are explicit but fragmented.
Workers increasingly expose permission, trust, environment, hook, MCP, extension, and transport semantics, but each does it differently.
Verification is becoming a worker capability.
Worker tools are adding review, multi-agent, eval, and curator-style verdict surfaces that can produce useful evidence but should not automatically become final truth.
Plugin, extension, and skill ecosystems are becoming the integration surface.
The practical power of worker CLIs is moving into plugins, hooks, extensions, skills, and transport modules.
Worker integrations are not durable doctrine.
Provider lists, release channels, app-server surfaces, and built-in integrations change quickly enough that wrappers must be thin and versioned.