Skip to main content

Gemini CLI

Gemini CLI is deprecated in Daintree. It still launches and resumes in the same project location, but is excluded from the Assistant picker.

Deprecated
Updated
Reviewed
Warning
Gemini CLI is deprecated in Daintree. The checked-in registry retains launch and resume support and lists it in the roster, but excludes it from the Daintree Assistant. Antigravity is the other Google CLI integration. These are Daintree integration decisions; whether your installed Gemini CLI can serve requests depends on its version and your Google account or key.

Gemini CLI

Gemini CLI is Google's CLI coding agent. It runs as a process in its own Daintree terminal panel with full PTY emulation, like every other built-in agent.

Commandgemini
ShortcutOption-Command-G Control-Alt-G Control-Alt-G
ColorBlue (#4285F4)
Bundled context estimate1,000,000 tokens
Default renderingAlt-screen escapes are blocked; output lands in Daintree's scrollback
Permission bypass--yolo (per agent or preset only)
Resumegemini --resume <session-id>, falling back to gemini -r latest
PlatformsmacOS, Windows, Linux

Install & Authenticate

See Google's current setup instructions for installation and sign-in.

Install from npm: npm install -g @google/gemini-cli. Run gemini and follow the prompts to authenticate. Daintree reads that state from ~/.gemini/oauth_creds.json, ~/.gemini/google_accounts.json, or GEMINI_API_KEY.

Google's transition announcement says that, since June 18, 2026, Gemini CLI no longer serves requests for personal Google accounts (free, Google AI Pro and Ultra); Google moved those users to Antigravity CLI. Gemini Code Assist Standard and Enterprise keep working, as do paid Gemini API keys and Gemini Enterprise Agent Platform keys. A fresh install signed in with a personal account will authenticate and then fail at the first request.

How Daintree Launches It

Gemini CLI's TUI takes the alternate screen buffer. Daintree blocks those escapes in the terminal, so output flows into its own scrollback and stays selectable.

Gemini is the one agent with a Share clipboard directory setting, on by default. It passes --include-directories for the temporary directory Daintree writes pasted clipboard images into, so Gemini can read them. Turn it off under Settings > CLI agents > Gemini > Launching if you would rather Gemini not see that directory.

Gemini's permission-bypass flag is --yolo, and Daintree injects it only when you turn bypass on for the agent or a preset. The global Skip permission prompts switch passes Gemini over: the agent doesn't declare bypass support, so the global override never turns it on for you.

Daintree's unified input completes Gemini's built-in / commands plus the custom TOML commands it finds under .gemini/commands, honoring GEMINI_CONFIG_DIR.

Daintree MCP servers

When the MCP server is on (Settings > MCP server) and the project's Agent integrations setting is Core or Full, or the project has turned on a plugin's agent tools, each new Gemini launch gets those servers in a system-defaults settings file named by GEMINI_CLI_SYSTEM_DEFAULTS_PATH. Gemini loads that file as its lowest-precedence settings layer and merges its mcpServers by name with yours. Because the variable replaces any system-defaults file an administrator set, Daintree carries that file's contents into its own. The file is written with owner-only permissions under Daintree's data folder and deleted when the terminal exits; nothing is written into your Gemini settings or the repository.

Resuming Sessions

Daintree captures Gemini's session ID and resumes with gemini --resume <session-id>. Quit cleanly with /quit so the ID is captured. When it isn't, the fallback is gemini -r latest; the latest argument is required, because a bare -r opens an interactive picker that blocks the terminal. For the resume mechanics across all agents, see Session Resume.

Note
Gemini's checkpoints are scoped by a hash of the folder path, and Daintree treats the retired CLI's conversations as unrecoverable across a project move; the move-or-rename preview says so. Keep the original project location when you need an existing conversation.

Integration reference

This guide describes Daintree's checked-in integration. Its agent definition records the launch command, install guidance, authentication probes, rendering capabilities, MCP wiring, and resume support. Authentication badges report local evidence; the CLI still owns sign-in and provider access. After changing an installation, use Re-check in Settings > CLI agents; restart Daintree if its inherited PATH has changed.