Frontier Roll-Up: April 22-May 6, 2026

The last two weeks were not about one winning coding agent. They were about worker tools becoming fuller environments.

Codex added persisted goals, which is the most important signal in this window: worker-native objectives are beginning to survive beyond a single prompt or session. Around that, Codex also expanded permission profiles, plugin workflows, external session import, and multi-agent controls. Claude Code pushed cloud multi-agent review, session recaps, plugin distribution, hook behavior, MCP governance, and telemetry attribution. Gemini CLI hardened workspace trust and environment loading while experimenting with reviewable memory patches. Hermes introduced a background Curator for skill-library maintenance. Pi kept its minimal-harness posture while rapidly changing providers, transports, extensions, and terminal rendering.

The pattern is clear:

The frontier changes. Your loop should compound.

Bitter should use the strongest worker surface available at the moment. It should not confuse that worker surface with the operator's durable loop.

Main Signals

Worker-Native Goals Are Emerging

Codex /goal is the strongest signal in this window. It is not just memory. It is a worker-native objective register: a way for a coding worker to carry a durable direction of travel across longer arcs of work.

That unlocks more serious long-horizon work, but it also creates a new authority question. A provider-native goal can guide a worker, but it should not silently become the operator's charter, mandate, or memory.

Bitter should receipt worker goals explicitly and reconcile them against CHARTER.md, the run mandate, and the wake packet.

Signal: 2026-05-06-worker-native-goals

Supported by:

• Codex finding

Worker-Native State Is Becoming a Memory Layer

Claude session recaps, Gemini Auto Memory, and Hermes Curator all point in the same direction: workers are learning how to carry context forward.

Bitter should leverage those surfaces, but receipt them as worker-native state: which recap, memory patch, skill report, or resume state governed the work, and what crossed back into operator-owned receipts and wake packets.

Signal: 2026-05-06-worker-native-memory

Supported by:

• Claude Code finding
• Gemini CLI finding
• Hermes Agent finding

Authority Semantics Are Explicit, But Fragmented

Codex expanded permission profiles and sandbox metadata. Gemini added secure .env loading, workspace trust, and shell allowlists. Claude's changelog moved around plugins, hooks, MCP, telemetry, and permission prompts. Pi's provider and extension layers changed quickly.

Bitter capability profiles should record the worker's actual trust and permission state: version, channel, env policy, sandbox/profile, plugin set, MCP surface, transport, and credential posture.

Signal: 2026-05-06-fragmented-authority-semantics

Supported by:

• Codex finding
• Claude Code finding
• Gemini CLI finding
• Pi Coding Agent finding

Verification Is Moving Into the Workers

Claude /ultrareview is the clearest signal: provider-native cloud fleets can review branches and PRs. Codex multi-agent controls, Gemini subagent/eval work, and Hermes Curator reports all rhyme with it.

Bitter should treat these as evidence producers, not final truth. The run contract still needs to say what evidence proves progress and what gets settled into memory.

Signal: 2026-05-06-worker-verification

Supported by:

• Claude Code finding
• Codex finding
• Gemini CLI finding
• Hermes Agent finding

Plugins, Extensions, and Skills Are the New Surface Area

Codex plugins, Claude plugins, Gemini extensions/MCP, Hermes skills, and Pi extension APIs are becoming the integration membrane.

Bitter adapters should record enabled plugin, extension, and skill surfaces. BitterLearn should not ingest worker-local skills or memories as durable Bitter memory without settlement.

Signal: 2026-05-06-plugin-extension-skill-surface

Supported by:

• Codex finding
• Claude Code finding
• Gemini CLI finding
• Hermes Agent finding
• Pi Coding Agent finding

Worker Integrations Are Not Doctrine

Pi removed built-in Gemini CLI and Antigravity support while adding many new providers. Gemini's stable, preview, and nightly channels differ materially. Codex alpha and app-server surfaces move quickly.

The durable layer is the run contract: charter, mandate, authority, execution, evidence, judgment, memory, and next run.

Signal: 2026-05-06-worker-integrations-not-doctrine

Supported by:

• Pi Coding Agent finding
• Gemini CLI finding
• Codex finding

What Operators Should Do

• Treat worker-native state as useful but not authoritative.
• Treat persistent worker goals as mission registers that must be reconciled against the operator's charter and run mandate.
• Record which goals, recaps, memories, plugins, skills, permission profiles, release channels, and transports were active during serious runs.
• Prefer worker tools that expose their trust, sandbox, plugin, session, and verification state clearly.
• Treat provider-native review as evidence, not final judgment.

What Bitter Should Do Next

1. Draft the adapter receipt vocabulary for worker-native state, permissions, plugin surfaces, verification outputs, and release-channel metadata.
2. Define worker_goal receipt fields and settlement rules for Codex /goal.
3. Build small probes for Codex /goal, Claude /ultrareview, Gemini workspace trust and memory patches, Hermes Curator output, and Pi session transport/extension metadata.
4. Create a worker capability matrix before deeper integration work.
5. Keep the public research loop conservative: no signal unless it can change the next action.

What Remains Uncertain

• Whether provider-native state will be stable enough for long-horizon work or remain tool-local convenience.
• Whether worker goals will remain single-worker convenience or become durable enough to coordinate ultra-long-horizon work under an operator charter.
• Whether cloud/native review surfaces produce evidence that is inspectable enough for Bitter receipts.
• Whether plugin and skill ecosystems will converge around common metadata or remain fragmented.
• Which worker surfaces expose enough permission, session, plugin, transport, and release-channel state for trustworthy Bitter adapters.

Supporting Findings

This roll-up is supported by source-backed findings from run 2026-05-06-manual-2026-04-22_2026-05-06-frontier-v0:

• Codex: Provider-Native Long-Horizon Work Is Moving Into the CLI
• Claude Code: Review, Recap, Plugins, and Permission Surfaces Are Converging
• Gemini CLI: Trust, Env Loading, Memory Patches, and Release Channels Matter
• Hermes Agent: The Self-Improving Personal-Agent Platform Is Hardening
• Pi Coding Agent: Thin Harness, Fast Provider Churn, and Extension Contracts

Structured signal records are in:

runs/2026-05-06-manual-2026-04-22_2026-05-06-frontier-v0/signals/frontier-signals.yml