Skip to content

fix(start): strip CI_* env vars in dev mode to prevent interactive hang #25649

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fuleinist wants to merge 1 commit into
base: main
Choose a base branch
from
+17 −0
Open

fix(start): strip CI_* env vars in dev mode to prevent interactive hang #25649

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions scripts/start.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,23 @@ const env = {
DEV: 'true',
};

// Filter out CI_* env vars to prevent is-in-ci from detecting CI environment,
// which would cause ink to switch to non-interactive mode in dev mode.
// The bundled build handles this via esbuild alias; dev mode needs this runtime fix.
// See issue #1563 and PR #22452.
const ciVars = Object.keys(env).filter((key) => key.startsWith('CI_'));
if (ciVars.length > 0) {
for (const key of ciVars) {
delete env[key];
}
console.warn(
`[gemini] Removed CI-related env vars to ensure interactive mode: ${ciVars.join(', ')}`
);
console.warn(
`[gemini] These variables are still available in processes spawned by shell tools.`
);
}

if (isInDebugMode) {
// If this is not set, the debugger will pause on the outer process rather
// than the relaunched process making it harder to debug.
Expand Down