Gemini CLI on every device you use

Gemini is the agent most likely to be running inside somebody else’s billing boundary rather than on a consumer login — a Google Cloud project and a location, read out of the shell environment of the process Happier starts. That is the part this page exists to say does not change.

It is also the one Google credential Happier stores. Connect a Gemini profile once and it is selectable at session start on any of your computers; the OAuth code is exchanged on the server and comes back as an encrypted bundle, so no Google OAuth secret is shipped inside the app you installed. Two ways in, depending on what you are holding: paste the redirect URL, or let the native apps open an in-app browser. On the web client it is the paste flow. When you would rather not connect anything, Happier reads the local signal instead — Gemini’s own environment variables, its config files, and a supported Google application-default credentials file — and the provider page will start gemini auth for you on the computer you picked.

Underneath that, Gemini takes MCP servers natively, so a server you defined once in Happier arrives as inventory rather than as a shell command it has to be told about. What the release does not offer for this one is a list of the Gemini sessions already on that computer, or a way to move vendor state to a second computer; a session you started through Happier resumes, and one you started in a bare terminal is not something the page will pretend to find. Skills you keep in .gemini/skills are picked up and travel with the session.

Gemini CLI is Google’s open-source terminal coding agent. happier gemini starts it in your repository with the environment your shell already has — which, in a lot of organisations, means a Google Cloud project and a location rather than a consumer login.

That deployment is the reason this page tends to matter. The agent runs inside your own billing and data boundary, and Happier only adds the transport: an encrypted session you can read on a phone, in a browser or on a second computer.

The iOS and Android apps, the desktop app for macOS, Windows and Linux, and app.happier.dev are all clients onto the Gemini CLI process running on your computer — not read-only mirrors. Answer a permission request, send the next instruction, browse the repository, read the diff. The transcript is end-to-end encrypted before it leaves your computer, so the server carrying it holds ciphertext.

Happier installs on the computer that already holds your repository, and happier gemini starts Gemini CLI there as an ordinary subprocess, in the directory you point it at, signed in the way you signed it in. There is no gateway between the agent and Google, and no copy of your source anywhere else.

Happier looks for gemini on your PATH first and runs the copy you installed. If there is not one, it can install @google/gemini-cli into ~/.happier/tools/providers/gemini/ — its own directory, not your global npm prefix. A copy you manage yourself is never replaced or upgraded behind your back.

Google’s own page for Gemini CLI is at goo.gle/gemini-cli-auth-docs. Happier does not mirror it, because a copy of someone else’s install instructions is a copy that goes stale.

Configuration reference for the Happier side — Gemini CLI in the Happier docs.

Gemini CLI is one of the agents Happier can point at a credential you connected once instead of at whatever that computer is logged into. It accepts a Gemini login.

Connected services are keyed by the credential, not by the agent, so the same Gemini login is selectable for every agent that can take it, on every computer you have connected — which is also what makes a pool of your own accounts useful across more than one of them. The credential is encrypted and decrypted on your own devices; the docs page carries the per-profile rules, because which kinds of profile each agent accepts is exactly the sort of detail that moves between releases.

Gemini CLI is one of 13 command-line coding agents Happier runs, and they share one session list, one permission inbox, one set of keyboard shortcuts and one MCP configuration.

You define an MCP server once and Gemini CLI receives it as native MCP inventory, next to whatever MCP servers it already had of its own.

That matters most on the days you are running more than one: sessions from different vendors side by side, and a notification tap opening the session that raised the request rather than the app’s front door. The full list is here.

Typing happier gemini in a terminal starts the session right where you are standing, and the same session is in the app at the same time. What you read in that shell is Happier’s own display of the session — the transcript, the permission prompts, the tool output — rather than Gemini CLI’s interface. Nobody has to give up the terminal to get a phone client.

There is no hand-off to Gemini CLI’s own TUI. That exists for Claude Code, Codex and OpenCode, and for Gemini CLI the session stays Happier’s on both ends. happier attach <session-id> lists the sessions on that computer and marks the ones it cannot reattach, rather than failing after you pick one.

The attach guide lists the cases instead of promising all of them.

One command on the computer that holds your code, then happier gemini in the repository you want to work in.

Walkthroughs are in the guides. All of it is MIT-licensed, and the relay is one you can run yourself.