Gemini CLI Proper

Use Gemini CLI as a bounded advisor or worker. Keep Codex responsible for final edits, validation, and the user-facing report unless the user explicitly asks Gemini to edit directly.

Guardrails

• Prefer signed-in Gemini CLI subscription auth. Do not use GEMINI_API_KEY or GOOGLE_API_KEY unless the user explicitly authorizes API-key usage.
• Before invoking Gemini, remove Gemini and Google API-key environment variables unless the user requested API billing.
• Use non-interactive prompt mode for delegated work: gemini -p "$PROMPT".
• Use --approval-mode plan for advisory work and audits.
• Use --skip-trust for headless runs inside known local repos.
• Prefer --output-format text for human-readable audits and --output-format json only when parsing is needed.
• Use the strongest available Gemini model for high-stakes research, architecture, long-context synthesis, and multimodal inspection; use Flash for quick summaries or low-stakes routing.
• Set a timeout and keep the task bounded. Gemini should inspect only the files, URLs, or artifacts required by the prompt.
• For code work, ask Gemini for findings, patch plans, or specific file suggestions first. Apply final edits in Codex unless a separate write-safe workflow is approved.
• Never allow destructive shell commands, credential access, deploys, git push, or broad filesystem edits from a delegated Gemini job.
• After Gemini returns, inspect and validate locally. Do not blindly trust its report.

Recommended Commands