Repository navigation
Conversation
|
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
c7f218a to
0399535
Compare
Review of the non-interactive tool execution fix:
|
e1e1f92 to
eb57ac0
Compare
|
this one's important too man |
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Issue for this PR
Closes #42773
Type of change
What does this PR do?
On Windows, tool commands that prompt on stdin (e.g.
npm execasking "Ok to proceed? (y)") hang — the prompt shows but nothing typed reaches the process, because the child stdin is an open pipe nothing closes and the TUI owns the console input.Changes:
CI=1,npm_config_yes=true,GIT_TERMINAL_PROMPT=0,NONINTERACTIVE=1, so tools like npm skip interactive prompts.How did you verify your code works?
Reproduced on Windows:
npm execwith an open stdin pipe hangs; withCI=1ornpm_config_yes=trueit completes. Checked no tests rely on the old default.Screenshots / recordings
N/A (not a UI change)
Checklist