From f814d2b58e427451b7b224911764e6dd0154e4fe Mon Sep 17 00:00:00 2001 From: slayerjain Date: Tue, 17 Nov 2026 23:56:43 +0530 Subject: [PATCH 1/6] docs: log in once to a self-hosted k8s-proxy The k8s-proxy auth section of the cloud replay page gains "Log in once on your own machine": `keploy login --k8s-proxy-url ` checks the API key at the proxy and saves the key and the URL in an owner-only ~/.keploy/cred.yaml, so later commands need neither KEPLOY_API_KEY nor KEPLOY_K8S_PROXY_URL. It covers `keploy login --show`, `keploy logout`, the one-time offer to save variables already exported (asked only in a terminal), the precedence (flag, environment, keploy.yml, saved login), and keeps the environment variables for CI. The CLI reference lists the login's --k8s-proxy-url and --show flags, says logout removes a saved login, and counts a saved login among what makes a run self-hosted for the update check. Signed-off-by: slayerjain --- .../keploy-cloud/cloud-replay.md | 20 +++++++++++++++++++ .../running-keploy/cli-commands.md | 6 ++++-- 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md index c11d4ac5e..6eb6ee20c 100644 --- a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md +++ b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md @@ -132,6 +132,24 @@ cloud: The two are related but conceptually distinct: [`--k8s-proxy-url`](#--k8s-proxy-url) chooses _which ingress the data plane targets_, while auth mode changes _how the CLI authenticates and which control-plane calls it makes_. In practice you just set the URL and auth mode comes on with it — you rarely pass `--k8s-proxy-auth` yourself. +### Log in once on your own machine + +On a machine you work from, save the login once instead of exporting `KEPLOY_API_KEY` and `KEPLOY_K8S_PROXY_URL` in every shell: + +```bash +keploy login --k8s-proxy-url https:// --api-key kep_xxxxxxxx +``` + +The CLI checks the key at that proxy and, only if the proxy accepts it, saves the key and the URL in `~/.keploy/cred.yaml` (`%USERPROFILE%\.keploy\cred.yaml` on Windows). Only you can read the file: it is mode `0600` on Linux and macOS, and has an owner-only ACL on Windows. A login the proxy refuses saves nothing. Without `--api-key` or `KEPLOY_API_KEY`, `keploy login` asks for the key when you run it in a terminal. + +Every later command on that machine finds both there, so `keploy cloud replay` and the other commands run with neither variable set. A saved login turns k8s-proxy-auth mode on for every command: pass `--k8s-proxy-auth=false` to leave it off for one run, or run `keploy logout` to remove the saved key and URL. + +`keploy login --show` prints the API key (its last 4 characters only) and the proxy URL a command uses, and where each one comes from: a flag, an environment variable, `keploy.yml`, or the saved login. It makes no network call. + +If you already export both variables, a command you run in a terminal offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. A run without a terminal (CI, a script, an editor extension that runs the CLI) never asks and never saves. + +Keep the environment variables in CI: a runner has no saved login, and the variables come from its secrets. + ### Enabling it | Input | Flag | Environment variable | keploy.yml | @@ -140,6 +158,8 @@ The two are related but conceptually distinct: [`--k8s-proxy-url`](#--k8s-proxy- | API key (PAT) | `--api-key` | `KEPLOY_API_KEY` | — | | Turn the mode on _(optional)_ | `--k8s-proxy-auth` | `KEPLOY_K8S_PROXY_AUTH=true` | `cloud.k8sProxyAuth: true` | +A [saved login](#log-in-once-on-your-own-machine) gives both the URL and the API key. When more than one source gives a value, the flag wins, then the environment variable, then `keploy.yml`, then the saved login. + Only two inputs are required — a proxy URL to reach and a PAT to authenticate. **Setting the proxy URL enables the mode automatically**, so `--k8s-proxy-auth` is optional; pass it (or `KEPLOY_K8S_PROXY_AUTH=true`) only to be explicit. Generate the PAT from **Settings → API Keys** in the dashboard. ```bash diff --git a/versioned_docs/version-4.0.0/running-keploy/cli-commands.md b/versioned_docs/version-4.0.0/running-keploy/cli-commands.md index bf9297560..1e1c8ef85 100755 --- a/versioned_docs/version-4.0.0/running-keploy/cli-commands.md +++ b/versioned_docs/version-4.0.0/running-keploy/cli-commands.md @@ -486,8 +486,10 @@ keploy login - `--no-wait` - Print the sign-in link and code and exit instead of waiting. Then run `keploy login --finish` to collect the session once you've approved it. Use this on a machine with no browser, or from a coding agent, whose shell shows a command's output only when it exits. - `--finish` - Collect the session for a sign-in that `keploy login --no-wait` started. It waits up to 70 seconds for your approval, and you can run it again until the code expires. - `--api-key string` - Use this Keploy API key for the command instead of `KEPLOY_API_KEY`. In CI, set `KEPLOY_API_KEY` from a secret instead of signing in. +- `--k8s-proxy-url string` - For a self-hosted cluster: check the API key (from `--api-key` or `KEPLOY_API_KEY`, or asked for in a terminal) at this k8s-proxy, then save the key and the URL in `~/.keploy/cred.yaml`, readable by you only. Later commands then need neither `KEPLOY_API_KEY` nor `KEPLOY_K8S_PROXY_URL`. A key the proxy refuses saves nothing. See [Log in once on your own machine](/docs/keploy-cloud/cloud-replay/#log-in-once-on-your-own-machine). +- `--show` - Print the API key (its last 4 characters only) and the k8s-proxy URL commands here use, and where each one comes from (a flag, an environment variable, `keploy.yml`, or the saved login), without signing in. -`keploy logout` signs you out. +`keploy logout` signs you out, and removes a saved self-hosted login (the API key and the k8s-proxy URL in `~/.keploy/cred.yaml`). ## [status](#status) @@ -574,7 +576,7 @@ Keploy doesn't replace its own binary in these cases: - **Keploy Docker image:** pull a newer image. - **Homebrew, Nix, or Snap:** Keploy prints a warning and runs on the version you have. Update through the package manager. - **VS Code extension:** the extension installs and tracks its own binary. Keploy only prints a notice that a newer release is available. -- **Self-hosted runs:** these runs reach only your k8s-proxy, so Keploy doesn't check for a release. A run is self-hosted when `--k8s-proxy-auth`, `--k8s-proxy-url`, `KEPLOY_K8S_PROXY_AUTH`, `KEPLOY_K8S_PROXY_URL`, or `cloud.k8sProxyAuth` or `cloud.k8sProxyUrl` in `keploy.yml` turns the mode on. +- **Self-hosted runs:** these runs reach only your k8s-proxy, so Keploy doesn't check for a release. A run is self-hosted when `--k8s-proxy-auth`, `--k8s-proxy-url`, `KEPLOY_K8S_PROXY_AUTH`, `KEPLOY_K8S_PROXY_URL`, `cloud.k8sProxyAuth` or `cloud.k8sProxyUrl` in `keploy.yml`, or a login saved by `keploy login --k8s-proxy-url` turns the mode on. - **Builds from an organization's release channel:** a build published under `keploy.io/ent/dl/org//` has a version with a suffix, such as `3.8.112-4f2a9c1d`. Keploy never replaces it with a public release, and `keploy update` leaves it alone too. Install new builds from the same channel. ## Related From 622e97ed4bd818daee5204be4fb97e412559a645 Mon Sep 17 00:00:00 2001 From: slayerjain Date: Wed, 18 Nov 2026 00:31:48 +0530 Subject: [PATCH 2/6] docs: say that keploy login --show reports k8s-proxy-auth mode keploy login --show now also prints whether k8s-proxy-auth mode is on and what turned it on or off: the --k8s-proxy-auth flag, the KEPLOY_K8S_PROXY_AUTH variable, a k8s-proxy URL (with keploy logout as the way back for a saved one), or keploy.yml's cloud.k8sProxyAuth. Signed-off-by: slayerjain --- versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md | 2 +- versioned_docs/version-4.0.0/running-keploy/cli-commands.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md index 6eb6ee20c..b7992a298 100644 --- a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md +++ b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md @@ -144,7 +144,7 @@ The CLI checks the key at that proxy and, only if the proxy accepts it, saves th Every later command on that machine finds both there, so `keploy cloud replay` and the other commands run with neither variable set. A saved login turns k8s-proxy-auth mode on for every command: pass `--k8s-proxy-auth=false` to leave it off for one run, or run `keploy logout` to remove the saved key and URL. -`keploy login --show` prints the API key (its last 4 characters only) and the proxy URL a command uses, and where each one comes from: a flag, an environment variable, `keploy.yml`, or the saved login. It makes no network call. +`keploy login --show` prints the API key (its last 4 characters only) and the proxy URL a command uses, and where each one comes from: a flag, an environment variable, `keploy.yml`, or the saved login. It also says whether k8s-proxy-auth mode is on, and what turned it on or off. It makes no network call. If you already export both variables, a command you run in a terminal offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. A run without a terminal (CI, a script, an editor extension that runs the CLI) never asks and never saves. diff --git a/versioned_docs/version-4.0.0/running-keploy/cli-commands.md b/versioned_docs/version-4.0.0/running-keploy/cli-commands.md index 1e1c8ef85..5b25685f4 100755 --- a/versioned_docs/version-4.0.0/running-keploy/cli-commands.md +++ b/versioned_docs/version-4.0.0/running-keploy/cli-commands.md @@ -487,7 +487,7 @@ keploy login - `--finish` - Collect the session for a sign-in that `keploy login --no-wait` started. It waits up to 70 seconds for your approval, and you can run it again until the code expires. - `--api-key string` - Use this Keploy API key for the command instead of `KEPLOY_API_KEY`. In CI, set `KEPLOY_API_KEY` from a secret instead of signing in. - `--k8s-proxy-url string` - For a self-hosted cluster: check the API key (from `--api-key` or `KEPLOY_API_KEY`, or asked for in a terminal) at this k8s-proxy, then save the key and the URL in `~/.keploy/cred.yaml`, readable by you only. Later commands then need neither `KEPLOY_API_KEY` nor `KEPLOY_K8S_PROXY_URL`. A key the proxy refuses saves nothing. See [Log in once on your own machine](/docs/keploy-cloud/cloud-replay/#log-in-once-on-your-own-machine). -- `--show` - Print the API key (its last 4 characters only) and the k8s-proxy URL commands here use, and where each one comes from (a flag, an environment variable, `keploy.yml`, or the saved login), without signing in. +- `--show` - Print the API key (its last 4 characters only) and the k8s-proxy URL commands here use, where each one comes from (a flag, an environment variable, `keploy.yml`, or the saved login), and whether k8s-proxy-auth mode is on and why, without signing in. `keploy logout` signs you out, and removes a saved self-hosted login (the API key and the k8s-proxy URL in `~/.keploy/cred.yaml`). From 84cdfa42311e41975178e25cb00ba718f72681e8 Mon Sep 17 00:00:00 2001 From: slayerjain Date: Wed, 18 Nov 2026 09:16:41 +0530 Subject: [PATCH 3/6] docs: say the saved-login offer comes after the run and never in CI A command run in a terminal with KEPLOY_API_KEY and KEPLOY_K8S_PROXY_URL exported now offers to save them only once it has finished successfully. The question waits 10 seconds at most, with no answer saving nothing, and never changes the exit code. A run in CI never asks, even when the runner gives it a terminal. Signed-off-by: slayerjain --- versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md index b7992a298..22b0a92e1 100644 --- a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md +++ b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md @@ -146,7 +146,7 @@ Every later command on that machine finds both there, so `keploy cloud replay` a `keploy login --show` prints the API key (its last 4 characters only) and the proxy URL a command uses, and where each one comes from: a flag, an environment variable, `keploy.yml`, or the saved login. It also says whether k8s-proxy-auth mode is on, and what turned it on or off. It makes no network call. -If you already export both variables, a command you run in a terminal offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. A run without a terminal (CI, a script, an editor extension that runs the CLI) never asks and never saves. +If you already export both variables, a command you run in a terminal runs as before and, once it has finished successfully, offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. The question waits 10 seconds at most: with no answer nothing is saved, and the next command asks again. The answer never changes the command's exit code. A run in CI never asks and never saves, even when the runner gives it a terminal (any CI variable, such as `CI`, `GITHUB_ACTIONS`, `GITLAB_CI` or `JENKINS_URL`, is enough), and neither does a run without a terminal (a script, an editor extension that runs the CLI). Keep the environment variables in CI: a runner has no saved login, and the variables come from its secrets. From 5b7977a483ba0c57f35234997d890ee4bb3a64bf Mon Sep 17 00:00:00 2001 From: slayerjain Date: Wed, 18 Nov 2026 11:02:52 +0530 Subject: [PATCH 4/6] docs: say where Windows keeps the login; its prompt hides the key On Windows the CLI keeps the login in .keploy under HOMEDRIVE+HOMEPATH, or USERPROFILE when those are not set. keploy login uses a saved key without asking, and its key prompt does not show what is typed. Signed-off-by: slayerjain --- versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md index 22b0a92e1..3e3b33cd8 100644 --- a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md +++ b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md @@ -140,7 +140,7 @@ On a machine you work from, save the login once instead of exporting `KEPLOY_API keploy login --k8s-proxy-url https:// --api-key kep_xxxxxxxx ``` -The CLI checks the key at that proxy and, only if the proxy accepts it, saves the key and the URL in `~/.keploy/cred.yaml` (`%USERPROFILE%\.keploy\cred.yaml` on Windows). Only you can read the file: it is mode `0600` on Linux and macOS, and has an owner-only ACL on Windows. A login the proxy refuses saves nothing. Without `--api-key` or `KEPLOY_API_KEY`, `keploy login` asks for the key when you run it in a terminal. +The CLI checks the key at that proxy and, only if the proxy accepts it, saves the key and the URL in `~/.keploy/cred.yaml` (on Windows, `.keploy\cred.yaml` in your home folder: `%HOMEDRIVE%%HOMEPATH%`, or `%USERPROFILE%` when those are not set). Only you can read the file: it is mode `0600` on Linux and macOS, and has an owner-only ACL on Windows. A login the proxy refuses saves nothing. Without `--api-key`, `KEPLOY_API_KEY` or a saved key, `keploy login` asks for the key when you run it in a terminal, and does not show it as you type. Every later command on that machine finds both there, so `keploy cloud replay` and the other commands run with neither variable set. A saved login turns k8s-proxy-auth mode on for every command: pass `--k8s-proxy-auth=false` to leave it off for one run, or run `keploy logout` to remove the saved key and URL. From 9d47d7adc9c9da77062c1735bb5b8938637a20d6 Mon Sep 17 00:00:00 2001 From: slayerjain Date: Wed, 18 Nov 2026 14:42:11 +0530 Subject: [PATCH 5/6] docs: say a background run is never asked to save the login A run sent to the background of its terminal is never asked, so the question cannot stop it, and an Enter typed while the command ran does not answer it. The key sources of keploy login --k8s-proxy-url include a login already saved. Signed-off-by: slayerjain --- versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md | 2 +- versioned_docs/version-4.0.0/running-keploy/cli-commands.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md index 3e3b33cd8..02d9778f8 100644 --- a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md +++ b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md @@ -146,7 +146,7 @@ Every later command on that machine finds both there, so `keploy cloud replay` a `keploy login --show` prints the API key (its last 4 characters only) and the proxy URL a command uses, and where each one comes from: a flag, an environment variable, `keploy.yml`, or the saved login. It also says whether k8s-proxy-auth mode is on, and what turned it on or off. It makes no network call. -If you already export both variables, a command you run in a terminal runs as before and, once it has finished successfully, offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. The question waits 10 seconds at most: with no answer nothing is saved, and the next command asks again. The answer never changes the command's exit code. A run in CI never asks and never saves, even when the runner gives it a terminal (any CI variable, such as `CI`, `GITHUB_ACTIONS`, `GITLAB_CI` or `JENKINS_URL`, is enough), and neither does a run without a terminal (a script, an editor extension that runs the CLI). +If you already export both variables, a command you run in a terminal runs as before and, once it has finished successfully, offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. The question waits 10 seconds at most: with no answer nothing is saved, and the next command asks again. The answer never changes the command's exit code. A run in CI never asks and never saves, even when the runner gives it a terminal (any CI variable, such as `CI`, `GITHUB_ACTIONS`, `GITLAB_CI` or `JENKINS_URL`, is enough), and neither does a run without a terminal (a script, an editor extension that runs the CLI) or one you sent to the background (`&`), so the question never stops a run. Only what you type after the question answers it: an Enter pressed while the command was still running does not. Keep the environment variables in CI: a runner has no saved login, and the variables come from its secrets. diff --git a/versioned_docs/version-4.0.0/running-keploy/cli-commands.md b/versioned_docs/version-4.0.0/running-keploy/cli-commands.md index 5b25685f4..20b8f9bdf 100755 --- a/versioned_docs/version-4.0.0/running-keploy/cli-commands.md +++ b/versioned_docs/version-4.0.0/running-keploy/cli-commands.md @@ -486,7 +486,7 @@ keploy login - `--no-wait` - Print the sign-in link and code and exit instead of waiting. Then run `keploy login --finish` to collect the session once you've approved it. Use this on a machine with no browser, or from a coding agent, whose shell shows a command's output only when it exits. - `--finish` - Collect the session for a sign-in that `keploy login --no-wait` started. It waits up to 70 seconds for your approval, and you can run it again until the code expires. - `--api-key string` - Use this Keploy API key for the command instead of `KEPLOY_API_KEY`. In CI, set `KEPLOY_API_KEY` from a secret instead of signing in. -- `--k8s-proxy-url string` - For a self-hosted cluster: check the API key (from `--api-key` or `KEPLOY_API_KEY`, or asked for in a terminal) at this k8s-proxy, then save the key and the URL in `~/.keploy/cred.yaml`, readable by you only. Later commands then need neither `KEPLOY_API_KEY` nor `KEPLOY_K8S_PROXY_URL`. A key the proxy refuses saves nothing. See [Log in once on your own machine](/docs/keploy-cloud/cloud-replay/#log-in-once-on-your-own-machine). +- `--k8s-proxy-url string` - For a self-hosted cluster: check the API key (from `--api-key`, `KEPLOY_API_KEY` or a login already saved, or asked for in a terminal) at this k8s-proxy, then save the key and the URL in `~/.keploy/cred.yaml`, readable by you only. Later commands then need neither `KEPLOY_API_KEY` nor `KEPLOY_K8S_PROXY_URL`. A key the proxy refuses saves nothing. See [Log in once on your own machine](/docs/keploy-cloud/cloud-replay/#log-in-once-on-your-own-machine). - `--show` - Print the API key (its last 4 characters only) and the k8s-proxy URL commands here use, where each one comes from (a flag, an environment variable, `keploy.yml`, or the saved login), and whether k8s-proxy-auth mode is on and why, without signing in. `keploy logout` signs you out, and removes a saved self-hosted login (the API key and the k8s-proxy URL in `~/.keploy/cred.yaml`). From 97d5b9387d0437429b4415555dcc01a122a5a20e Mon Sep 17 00:00:00 2001 From: slayerjain Date: Wed, 18 Nov 2026 23:50:17 +0530 Subject: [PATCH 6/6] docs: say a run moved to the background stops waiting for the answer A self-hosted run asked to save its login and moved to the background while the question waits (Ctrl-Z, then bg) stops waiting at once and saves nothing, as the CLI now does. Signed-off-by: slayerjain --- versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md index 02d9778f8..c9f26347f 100644 --- a/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md +++ b/versioned_docs/version-4.0.0/keploy-cloud/cloud-replay.md @@ -146,7 +146,7 @@ Every later command on that machine finds both there, so `keploy cloud replay` a `keploy login --show` prints the API key (its last 4 characters only) and the proxy URL a command uses, and where each one comes from: a flag, an environment variable, `keploy.yml`, or the saved login. It also says whether k8s-proxy-auth mode is on, and what turned it on or off. It makes no network call. -If you already export both variables, a command you run in a terminal runs as before and, once it has finished successfully, offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. The question waits 10 seconds at most: with no answer nothing is saved, and the next command asks again. The answer never changes the command's exit code. A run in CI never asks and never saves, even when the runner gives it a terminal (any CI variable, such as `CI`, `GITHUB_ACTIONS`, `GITLAB_CI` or `JENKINS_URL`, is enough), and neither does a run without a terminal (a script, an editor extension that runs the CLI) or one you sent to the background (`&`), so the question never stops a run. Only what you type after the question answers it: an Enter pressed while the command was still running does not. +If you already export both variables, a command you run in a terminal runs as before and, once it has finished successfully, offers once to keep them: `Save the API key and k8s-proxy URL to ~/.keploy for next time? [Y/n]`. Your answer is remembered for that key and URL, so you are not asked again; a different key or URL asks again. The question waits 10 seconds at most: with no answer nothing is saved, and the next command asks again. The answer never changes the command's exit code. A run in CI never asks and never saves, even when the runner gives it a terminal (any CI variable, such as `CI`, `GITHUB_ACTIONS`, `GITLAB_CI` or `JENKINS_URL`, is enough), and neither does a run without a terminal (a script, an editor extension that runs the CLI) or one you sent to the background (`&`). If you move a run to the background while the question waits (Ctrl-Z, then `bg`), it stops waiting at once and saves nothing, so the question never holds a run in the background. Only what you type after the question answers it: an Enter pressed while the command was still running does not. Keep the environment variables in CI: a runner has no saved login, and the variables come from its secrets.