Quick answer
Gemini CLI can use a permitted local shell tool, which can run an already configured SSH or SFTP client. The hosting connection is separate from your Gemini login. Run the agent in a local project, keep its permissions narrow, and deploy only reviewed changes to the exact account and domain.
Before you start
Use Google's current official tool and authentication guidance. Confirm the product and entitlement actually available to your account, since Gemini web chat, Gemini CLI, and other Google coding tools are not interchangeable. Your hosting account must support the chosen transfer or shell method.
What to do
- Set up a local source folder or repository and take a baseline copy. Keep secrets and production customer data outside the material supplied to the agent.
- Test SSH or SFTP in your normal terminal with the correct username, server, port, and key before asking Gemini to use it.
- Explain the project boundaries and request a plan and read-only inspection first. Review shell and file-write approval prompts rather than bypassing them.
- Make the change locally, inspect the diff, run tests, and approve deployment only after a current backup of the remote files and database where relevant.
Check the result
Read back deployed files and test the public URL, including any forms or checkout affected. Keep a specific rollback artifact rather than relying on the conversation to reconstruct the old version.
If something does not work
If the shell tool or network is unavailable, use a supported local workflow and your regular deployment client. Installing an arbitrary extension is not a safe way to add access to a production account.
Related help
- Write a useful brief for an AI website coding assistant
- Choose SSH, SFTP or an approved cPanel API operation
- Review an AI-generated website change before deployment
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
