$ the-wire · showcase
Codex pauses Bazel release artifacts for Cargo-only builds
By RepoJournal · Filed · About Agentic Coding · Composed from the cited sources · methodology
Codex cut Bazel out of its release pipeline after a revoked BuildBuddy key, Goose turned off thinking display by default, and OpenHands spent the day making a slow, noisy agent UI behave.
Make Bazel checks advisory and pause Bazel release artifacts (#58717) openai/codex
Codex dropped Bazel from the `blocking-ci` required dependencies and made the Bazel-backed argument comment lint and SDK jobs advisory, because the BuildBuddy key is revoked. Release build and packaging matrices are now restricted to Cargo, including Windows, so Bazel artifacts simply will not appear for upcoming releases.
Remove Bazel outputs from DotSlash release configs (#58757) openai/codex
The DotSlash release configs no longer reference Bazel outputs for Codex, the Windows command runner and sandbox setup, or the provisioned macOS packages, since those assets are absent from the Cargo-only fixture for `0.167.0-alpha.2`. If you install or pin Codex through those DotSlash configs, expect the configured output set to shrink.
feat(desktop): collapse thinking by default and add a setting for it aaif-goose/goose
Desktop now collapses the thinking block by default, including while the model is thinking, and a new Show Thinking setting under Settings > Chat (Response Styles card) switches it between always, collapsed and never. The choice persists in `settings.json` as `showThinking`, defaulting to `collapsed`.
fix: retry initial Cloud history failures before socket fallback OpenHands/OpenHands
A failed initial Cloud history request was being converted into an empty successful page because of its sort parameter, which skipped the query retry and left the transcript leaning on runtime replay. With recovery fixed, the first saved message appears in 3.4 seconds in the PR's controlled recording, down from 12.5. Toast spam was among the stated reasons for the fix.
fix: keep connection recovery quiet OpenHands/OpenHands
A momentary WebSocket interruption no longer surfaces as "Unable to connect to server" while recovery is still running. Idle conversations stay silent, and only the selected agent's last-known running state shows recovery progress after thirty seconds, with Retry appearing after sixty.
Extract fresh session adoption from TUI session startup openai/codex
The long tail is internal: OpenHands finished its agent-friendly linting pass by naming compact metadata sizes, plus startup and title-handoff layout fixes, while OpenCode deduplicated its built-in tools, pty and git helpers in behavior-preserving refactors.
