How to Change the Gemini CLI Working Directory

The Gemini CLI — Google's command-line interface for interacting with Gemini AI models — operates within a specific working directory context, just like any other terminal-based tool. Knowing how to change or configure that directory affects where the CLI reads files from, where it writes output, and how it resolves relative paths in your commands. If you've been getting unexpected file-not-found errors or outputs landing in the wrong folder, the working directory is usually the first place to investigate.

What the Working Directory Actually Controls

When you run the Gemini CLI, it inherits the current working directory (CWD) from your terminal session at the time of execution. This means:

• File inputs (like passing a local document to a prompt) are resolved relative to that directory
• Output files, if specified by path, are written relative to that same location
• Config files or .env files the CLI looks for locally will be searched from that root

This is standard Unix/Windows shell behavior, not something unique to Gemini CLI. But because AI CLIs often deal with files as context — feeding documents into prompts, saving responses — the working directory matters more here than it might for a simple utility.

The Standard Way: Change Directory Before Running 🗂️

The most direct method is to change your terminal's working directory before invoking the CLI.