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.tsfromqueueMicrotasktosetTimeout(resolve, 10). - The same PR adds
--ignore-scriptsto workspace package publishing and extends the parallel-tools integration test timeout. different-ai/openworkcommit 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.