google-gemini/gemini-cli

What happened? formatDuration() in packages/cli/src/ui/utils/formatters.ts chooses the unit from the raw value and only rounds afterwards, so values just under a boundary round up to a reading that the next unit should have taken: formatDuration(999.4); // '999ms' formatDuration(999.5); // '1000ms' expected '1.0s' formatDuration(59949); // '59.9s' formatDuration(59950); // '60.0s' expected '1m' formatDuration(59999); // '60.0s' expected '1m' ms < 1000 is checked before Math.round, and seconds < 60 is checked before toFixed(1). This is visible in /stats and /stats model: average latency is totalLatencyMs / totalRequests, so it is usually fractional and can print as "1000ms", and agent active / API / tool time can print as "60.0s". Checked on current main (c9096a8) by calling the function directly under vitest. What did you expect to happen? Values that round up to the next unit should be shown in that unit: "1.0s" instead of "1000ms", and "1m" instead of "60.0s". Client inform

What happened? I'm running Gemini CLI locally on arch linux with the podman sandbox enabled: GEMINI_SANDBOX=podman When i run npm start, the CLI gets to the point where it rebuilds one of the native dependencies inside the sandbox, but the rebuild fails, i've attached the full output below. This seems to be related to how the sandbox handles UID/GID mapping with rootless podman. From what I understand, the current flow creates a user inside the container with the same UID/GID as the host user and then runs Gemini as that user. That works when the container UID maps directly to the host UID, but rootless Podman normally uses a user namespace, so that's not necessarily the case. Because the project is bind-mounted into the container, this can result in files being owned by a UID that the host user can't modify. In my case, that eventually shows up as node-gyp being unable to remove the build directory. What did you expect to happen? If the sandbox is using rootless podman and UID/GID ma

What would you like to be added? Went through the repo and found that there is no image generation models like nano banana in the model configs. Shall I add it ? Thankyou. Why is this needed? Image generation is widely used everywhere, and accessing it via cli is equally important. Additional context No response

Bug Report: Trailing . in antigravity.google URL causes link to not load Description When signing in with Google fails in Gemini CLI, the error message displays a URL with an extra trailing period (.) appended to it. This makes the URL invalid and it fails to load in a browser. Steps to Reproduce Run gemini CLI Select "Sign in with Google" from the authentication options Observe the error message displayed Try to open the URL shown in the error message Current Behavior The error message reads: Failed to sign in. Message: This client is no longer supported for Gemini Code Assist for individuals. To continue using Gemini, please migrate to the Antigravity suite of products: https://antigravity.google. The URL is https://antigravity.google. — note the extra trailing period at the end. When clicked or copied into a browser, it resolves to https://antigravity.google. which is an invalid domain and does not load. Expected Behavior The URL should be: https://antigravity.google (without

What happened? In the VS Code companion extension (packages/vscode-ide-companion/src/extension.ts), the activate() function pushes its Disposables into context.subscriptions in two context.subscriptions.push(...) calls. In each call, two registrations are wrapped in an extra pair of parentheses, which turns them into a single comma expression instead of separate arguments: // group 1 (vscode.commands.registerCommand('gemini.diff.accept', ...), vscode.commands.registerCommand('gemini.diff.cancel', ...)), // group 2 (vscode.workspace.onDidChangeWorkspaceFolders(...), vscode.workspace.onDidGrantWorkspaceTrust(...)), A comma expression evaluates both operands but its value is only the last one. So both registrations actually run (the command and listener are created), but only the second Disposable of each group (gemini.diff.cancel, onDidGrantWorkspaceTrust) is passed to push() and tracked in context.subscriptions. The gemini.diff.accept command Disposable and the onDidChangeWorkspaceFo