Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Gemini CLI 0.67 lists models, fixes a timeout

Written November 8, 2026

Gemini CLI 0.67.0 adds a models command and fixes a Claude hook migration that shrank timeouts 1000x. The gotcha to check after upgrading.

What shipped

Gemini CLI v0.67.0 shipped on November 4 with 27 listed changes: two features and 22 fixes. The feature most people will notice first is a models command with a --list-models flag for model discovery. Until now there was no direct way to see which models you could pass to -m without starting an interactive session. Now gemini models lists them from the terminal, which makes the choice scriptable: a script can check what is available before it picks a model, instead of hard-coding a name and failing later.

The second feature bridges the IDE companion into container sandboxes over exec stdio, so the companion keeps working when the CLI runs inside a container sandbox. The rest of the release is fixes, including duplicate agent loading when the workspace is the home directory, and display width for Thai and Lao characters.

The timeout gotcha

The fix that matters most is a one-line description with a large consequence: the release converts the Claude hook timeout from seconds to milliseconds during migration. Claude Code measures a hook timeout in seconds; Gemini CLI measures it in milliseconds. A migration that copied the number across without converting the unit shrank the timeout a thousand times. A Claude hook set to timeout: 600 — ten minutes — became 600 milliseconds on the Gemini side, short enough that almost any command times out immediately.

Version 0.67.0 fixes the migration, so hooks migrated from now on get the conversion. But the fix does not repair hooks that were already migrated with the wrong unit. If you migrated Claude hooks before upgrading, check every timeout value after upgrading: a hook that worked before the migration and then started timing out for no visible reason was probably carrying a seconds value read as milliseconds. Multiply the migrated value by 1,000 to get the intended duration back, and compare it against the original Claude configuration rather than trusting the migrated file.

The practical check is short. Open the hook configuration you migrated, find each timeout, and ask what unit it was written in. Anything in the low hundreds that was meant to be minutes is suspect. The default on the Gemini side is 60,000 milliseconds — a hook timeout near 600 where the original said 600 seconds is the signature of this bug.

What it is not

The models command is a discovery tool, not a model upgrade: it lists what the CLI can use, and changes nothing about which model runs your prompts. The timeout fix is a migration fix, not a change to how timeouts work: the unit on the Gemini side was always milliseconds, and the bug was in the conversion, not the setting.

One more note, because a wrong claim is circulating: Gemini CLI was not retired on November 1. Version 0.67.0 shipped on November 4, with a full changelog, which is not what a retired tool looks like. The models command is new enough that it had not yet reached the official documentation when the release landed — check --help locally for the output format rather than the docs page.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Run parallel subagents in Claude Code · Claude Code sent your email to websites · Google ADK 2.14: A2A graduates, Teams joins in