Bitter Frontier
Founding member access recorded.
Checkout cancelled.

Research Version

Partial cycle: testing Profile doctrine on Gemini CLI

2026-05-11-partial-cycle-2026-05-08_2026-05-11-frontier-v0

Status
draft
Window
2026-05-08 to 2026-05-11
Signals
1

Mode: partial_profile_cycle_test

Source contracts

Accepted signals from this run

  1. Gemini CLI Subagents become pluggable; sessions become portable

Artifact contents

Every file the loop produced for this run, anchored in the repo. Internal links go to the rendered page; the repo path opens the raw artifact on GitHub.

Run digest

The big move is architectural: Gemini's subagents are no longer just approval-mode aware; they now sit behind a pluggable AgentProtocol with both local and remote backends. The split forces a previously implicit question — where does delegated work actually run — into a surface that can be inspected and configured. Pair this with a new session export/import capability and Gemini's loop now treats agent identity and agent state as serialisable objects rather than ambient context.

The v0.41.0 stable release also extends two existing authority claims: workspace trust now enforces in headless mode, and shell command validation gains a core-tools allowlist. Neither is a category-creating change, but together they close the obvious gaps where the previous evidence stopped.

What To Try

  • If you delegate work via Gemini's subagents, examine which protocol variant your run actually used and whether your trust assumptions still hold.
  • If your CI uses Gemini in non-interactive contexts to bypass workspace trust prompts, that path is now closed. Re-run with explicit trust state.
  • Try exporting a session, inspecting the file, and rehydrating it on a different machine to learn what state actually crosses the wire.

What Remains Uncertain

  • The session export format's coverage is not documented in the commit: whether accepted memory patches, approval-mode state, and active MCP connections cross the wire is the next probe.
  • RemoteSubagentProtocol ships with tests but no observed remote target. Whether a remote subagent runs on a Google-hosted surface or a user-controlled one is not yet established.