Connect while to Gemini CLI in 2026: the command and the authorization
Gemini CLI already writes your code. Connected to while over MCP, it also puts it on while, with its data, and leaves what matters for you to approve. Here is the connection, the authorization, and what Gemini CLI can do next.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
Gemini CLI already writes your code. Connected to while over MCP, it also puts it on while: while builds the code, runs its tests, gives it an HTTPS address, watches it and tells you when it breaks2. The connection takes a minute, and you stay in control of what matters.
The short version. One terminal command is enough. On the first call, while opens a page in your browser: you choose where Gemini CLI acts, one tool or the whole organization, and its level, Read, Read and act, or Administer. What matters, like a production release, then waits for a person’s approval.
The connection at a glance
| The moment | What you do |
|---|---|
| Connect | One command, below |
| Authorize | A page in the browser: the tool or the organization, and the level |
| Try without an account | The trial server, named while-essai |
| No browser, in CI | A token in the Authorization header, confirmed with a link |
Step 1: connect while to Gemini CLI
gemini mcp add --scope user --transport http while https://app.while.sh/mcp
To connect every AI tool on your computer at once, while’s install script does the same thing2:
curl -fsSL https://app.while.sh/install.sh | sh
Step 2: authorize Gemini CLI
Ask Gemini CLI for a first action on while. On the first tool call, while opens the authorization page in your browser: you sign in, then choose where Gemini CLI acts, one tool or the whole organization, and its level, Read, Read and act, or Administer2. Then open a new Gemini CLI session so while shows up among its tools2.
You, to your AI: Put this tool on while, with its data, and keep it for the team.
What Gemini CLI does next
Over MCP, Gemini CLI puts the tool on while, reads logs and errors, queries the data and rolls back when a version causes trouble2.
- Put the tool on while. Gemini CLI writes the while.yaml file, sends the code, and while builds it, runs its tests and returns the address.
- Understand an error. Gemini CLI reads the logs and the errors grouped in while, finds the cause and fixes it.
- Roll back. If the latest version breaks something, Gemini CLI puts the previous one back.

What waits for your approval
Some actions wait for a person, and Gemini CLI gives you the link. A production release, deleting a database, an outside API or an access: a person in the organization decides. At the Read and act level, an administration action, like adding a person, creating a token or granting a role, is confirmed with one click2. Your AI never approves.
The credentials of your software stay in while, and Gemini CLI never sees them. The details are on our security page, and in connect an API with no credentials in the code.
Without an account: the trial
The trial server, https://app.while.sh/essai, needs no sign-in: the same commands, named while-essai. The tool has its address for a limited time, and Gemini CLI gives you a link to keep it by creating your account2.
Once the tool is on while, keep it for your colleagues with their email account, or share it with a client through a link and a password. The same guides exist for Claude Code, Codex and Cursor.
Try it with Gemini CLI
Give this message to Gemini CLI. The trial is free, with no sign-up, and your tool has its address in 3 minutes.
Read while.sh/agents and help me get started with while.
Sources
- Gemini CLI, MCP servers, accessed November 19, 2026
- while, the page for AI tools, accessed November 19, 2026