Repository navigation
[Bug]: Shell command failure on win32 platform due to Unix-style export causing excessive retries #9797
Closed as not planned
Description
Description
The automated agent environment consistently prepends a Unix-style environment variable export string (export CI=true ...;) to all bash tool commands. On Windows systems, export is not a recognized command.
Critically, when this failure occurs, the agent logic appears to repeatedly retry the command multiple times in a tight loop. This results in a cascade of "not recognized" errors and prevents the task from failing gracefully or proceeding.
Plugins
oh-my-opencode
OpenCode version
1.1.25
Steps to reproduce
- Type anything that triggers a bash command execution (e.g., git status)
- Observe the command being prefixed with export ...;
- The command fails immediately because export is not a valid Windows command.
- The system automatically retries the same malformed command multiple times (observed 4+ consecutive attempts in one session), cluttering the logs and stalling execution.
Screenshot and/or share link
Operating System
Windows11
Terminal
Windows Terminal
Activity
github-actions commentedon Jan 21, 2026
This issue might be a duplicate of existing issues. Please check:
shell: process.platform === 'win32'configuration)The root cause appears to be related to how bash commands are executed on Windows. The excessive retries you're experiencing might be tied to the transient spawn failures mentioned in #6488, or the shell configuration issue in #8160.
Feel free to ignore if none of these address your specific case.
lvmax1998 commentedon Jan 22, 2026
The same error occurred in version v1.1.29.
pschiel commentedon Jan 22, 2026
This is no opencode issue. There is nothing in opencode that would produce these bash exports.
Your plugin does that.