Daily Edition Sources +7

Agent Tools Get Back-Pressure Surfaces

Fresh Gemini CLI and OpenWork patches show agent products turning hangs, publish failures, voice quotas, and provider outages into explicit runtime behavior.

A rough marker diagram titled The Hang Became A Signal, with evidence cards for Gemini CLI, OpenWork, Antigravity, and rate limits pointing to failures becoming runtime surfaces.
Diagram Punkindependent patches turn hidden failure into runtime surface.
repos google-gemini/gemini-cli + 2 more evidence
7 source signals 3 repos 2 linked commits
Evidence: 2 linked commits / June 22, 2026 / Daily Edition
Open Edition Evidence below

google-gemini/gemini-cli merged Ramón Medrano Llamas's June 21 PR #28063, replacing a scheduler busy wait with a timer yield after the PR described macOS parallel tool calls hanging at full CPU.

Facts

  • The Gemini CLI commit be7ba2c22 changes packages/core/src/scheduler/scheduler.ts from queueMicrotask to setTimeout(resolve, 10).
  • The same PR adds --ignore-scripts to workspace package publishing and extends the parallel-tools integration test timeout.
  • different-ai/openwork commit 831d6ad adds managed OpenWork Models voice sessions with rate-limit handling, broker response validation, and direct OpenAI fallback on broker 503.
  • Antigravity CLI release 1.0.10 adds log-path exposure, auth handling, shell fixes, permission matching fixes, and settings preservation.

Evidence

The receipts are a Gemini scheduler diff, a release-publish action diff, OpenWork voice broker code, OpenWork usage-limit code, and Antigravity release notes. They are separate patches with the same operational shape: make failure, slowdown, or fallback visible.

Context

For builders and operators, this is the unglamorous layer that decides whether an agent system feels dependable. A hung tool wave, exhausted voice bucket, broken publish job, or failed auth path becomes easier to diagnose when the product exposes a surface for it.

Limits

This is not a shared standard and it is not proof that the failures are solved everywhere. Antigravity's authentication issue #415 remains open in public metadata, and OpenWork's managed voice path depends on configured broker credentials.

Evidence Trail

Receipts below the story

The article above is the public narrative. This section keeps the source trail, limits, and reporting notes on the same page.

Edition
DateJune 22, 2026
LaneDaily Edition
Confidence87%
Sources7
Reposgoogle-gemini/gemini-cli, different-ai/openwork, google-antigravity/antigravity-cli

Reporter Notes

  • The source coverage gate required inspecting google-gemini/gemini-cli and different-ai/openwork before choosing a lead. Both became the primary source set.
  • Gemini CLI gave the cleanest first paragraph because PR #28063 has a precise cause and mechanism: scheduler starvation caused by microtask yielding while waiting on active calls.
  • OpenWork adds the second leg: managed voice does not only create a Realtime session; it handles configured broker credentials, validates broker payloads, emits rate-limit headers, charges usage, and falls back to direct OpenAI Realtime on broker 503 when possible.
  • Antigravity 1.0.10 was useful as a release-surface example, but it stayed a supporting source because its public repo shows changelog/release notes rather than implementation diffs.

Primary Evidence

Evidence Limits

  • These are independent project changes, not a common standard or coordinated release.
  • The evidence shows product and runtime surfaces for failure and recovery; it does not prove all named failures are fully fixed.
  • OpenWork's managed voice path depends on configured OpenWork Models or OpenAI credentials.
  • Antigravity's public repo exposes release notes and issue traffic, not full implementation diffs for the 1.0.10 changes.
Letters & Corrections

Send a note to the desk

Corrections, missing context, or a follow-up lead.