$ the-wire · showcase
Goose fixes Gemini thinking levels, opencode adds machine paths
By RepoJournal · Filed · About Agentic Coding · Composed from the cited sources · methodology
Goose made Gemini 4 thinking effort actually reach the API and stopped leaking ACP headers to disk, while opencode's multi-machine work landed behind a flag and gemini-cli shipped v0.70.0 with a Windows spinner freeze fix.
fix(google): send thinking levels to Gemini 4 and later, including xhigh aaif-goose/goose
Until now, moving the thinking-effort setting from off to max on gemini-4-neon through the Google provider changed nothing, because goose sent no thinkingConfig for Gemini 4 at all; each setting now sends a real thinkingLevel, xhigh included. The author flags that the PR is parked pending triage of the underlying issue, so expect it in a release rather than today.
feat(providers): add Gemini 4 Neon to the model catalog aaif-goose/goose
gemini-4-neon had no entry in canonical_models.json, so goose capped its output at 4,096 tokens, did not treat it as a reasoning model, and could not read its thinking levels from the catalog, which meant Max effort never sent xhigh. The PR adds 23 neon entries generated from models.dev, mirroring how argon, carbon and hydrogen are handled. Worth pairing with the provider fix if you run Gemini ...
feat(acp): treat all headers as secret in mcpServers configs over ACP aaif-goose/goose
ACP clients resend mcpServers on load and fork, so goose was writing their HTTP header values into the session database; header values now stay in memory with only placeholders persisted, and changing a value restarts the extension with the new header. Scope matters: this covers ACP mcpServers only, Goose-specific extension configs are unchanged, and existing session records are not scrubbed.
feat(core): machine names in paths anomalyco/opencode
With the machines flag on, a tool path can name another computer, so gpu:/work/train.py reads, writes, edits, patches, lists and runs commands on the machine called gpu; with the flag off every path resolves exactly as it does today. Nothing outside tests can add a machine yet, so this is one to watch rather than adopt.
fix(core,cli): parse PowerShell commands asynchronously to prevent UI spinner freeze google-gemini/gemini-cli
Gemini CLI's PowerShell validation used a blocking spawnSync without per-invocation caching, stalling the Node.js event loop up to 14 times and freezing the Thinking spinner and elapsed-time counter for seconds on Windows. The fix parses PowerShell commands asynchronously; it lands alongside the v0.70.0 release. Also in gemini-cli: GitIgnoreParser no longer drops files re-included by a nested ....
Action items
- → Upgrade gemini-cli to v0.70.0 if you run PowerShell commands on Windows google-gemini/gemini-cli [plan]