diff options
| -rw-r--r-- | docs/troubleshooting.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index ef9e9238..0d54afde 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -49,6 +49,11 @@ This guide provides solutions to common issues and debugging tips. - **Cause:** If sandboxing is enabled, then the application is likely attempting an operation restricted by your sandbox, such as writing outside the project directory or system temp directory. - **Solution:** See [Sandboxing](./cli/configuration.md#sandboxing) for more information, including how to customize your sandbox configuration. +- **CLI is not interactive in "CI" environments** + - **Issue:** The CLI does not enter interactive mode (no prompt appears) if an environment variable starting with `CI_` (e.g., `CI_TOKEN`) is set. This is because the `is-in-ci` package, used by the underlying UI framework, detects these variables and assumes a non-interactive CI environment. + - **Cause:** The `is-in-ci` package checks for the presence of `CI`, `CONTINUOUS_INTEGRATION`, or any environment variable with a `CI_` prefix. When any of these are found, it signals that the environment is non-interactive, which prevents the CLI from starting in its interactive mode. + - **Solution:**: If the `CI_` prefixed variable is not needed for the CLI to function, you can temporarily unset it for the command. e.g., `env -u CI_TOKEN gemini` + ## Debugging Tips - **CLI debugging:** |