[Bug]: Shell command failure on win32 platform due to Unix-style export causing excessive retries

[lvmax1998]

Prerequisites

• I have searched existing issues to avoid duplicates
• I am using the latest version of oh-my-opencode
• I have read the documentation

Bug 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.

Steps to Reproduce

1. Type anything that triggers a bash command execution (e.g., git status)
2. Observe the command being prefixed with export ...;
3. The command fails immediately because export is not a valid Windows command.
4. The system automatically retries the same malformed command multiple times (observed 4+ consecutive attempts in one session), cluttering the logs and stalling execution.

Expected Behavior

Running git status no longer reports an error.

Actual Behavior

Error: 'export' is not recognized as an internal or external command,
operable program or batch file.

Doctor Output

Installation
────────────────────────────────────────
  ✗ OpenCode Installation → OpenCode is not installed
  ✓ Plugin Registration → Registered (pinned: latest)

Configuration
────────────────────────────────────────
  ✓ Configuration Validity → Valid JSON config

Authentication
────────────────────────────────────────
  ✓ Anthropic (Claude) Auth → Auth plugin available
  ○ OpenAI (ChatGPT) Auth → Auth plugin not installed
  ✓ Google (Gemini) Auth → Auth plugin available

Dependencies
────────────────────────────────────────
  ⚠ AST-Grep CLI → Not installed (optional)
  ⚠ AST-Grep NAPI → Not installed (optional)
  ⚠ Comment Checker → Not installed (optional)

Tools & Servers
────────────────────────────────────────
  ⚠ GitHub CLI → Not installed (optional)
  ⚠ LSP Servers → No LSP servers detected
  ✓ Built-in MCP Servers → 2 built-in servers enabled
  ○ User MCP Configuration → No user MCP configuration found

Updates
────────────────────────────────────────
  ✓ Version Status → Up to date (2.14.0)

Summary
────────────────────────────────────────

  6 passed, 1 failed, 5 warnings, 2 skipped
  Total: 14 checks in 630ms

Error Logs

Configuration

Additional Context

No response

Operating System

Windows

OpenCode Version

1.1.29

[stevewang1]

I am currently analyzing these issues to help a user on Windows. Your insights on the 'export' bug in #983 are particularly valuable.

[lvmax1998]

I am currently analyzing these issues to help a user on Windows. Your insights on the 'export' bug in #983 are particularly valuable.

I don't understand—doesn't this still fail to resolve the issue where the agent running the git status command on Windows systems throws the error “‘export’ is not recognized as an internal or external command”?

[Lycidas97]

set "disabled_hooks": ["non-interactive-env"] in oh-my-opencode.json could temporary fix this.

[lvmax1998]

set "disabled_hooks": ["non-interactive-env"] in oh-my-opencode.json could temporary fix this.

Thanks, but I used a different approach instead—I just created a new export.cmd file:

@echo off
REM usage：export VAR1=value1 VAR2=value2 ...; command args

setlocal EnableDelayedExpansion

set "_INPUT=%*"
set "_TMPFILE=%TEMP%\_export_%RANDOM%.cmd"

echo @echo off > "!_TMPFILE!"
set "_FOUND_SEMI=0"

for /f "tokens=1,* delims=;" %%A in ("!_INPUT!") do (
    set "_ENV_VARS=%%A"
    set "_COMMAND=%%B"
    if not "%%B"=="" set "_FOUND_SEMI=1"
)

:parse_vars
if "!_ENV_VARS!"=="" goto execute
for /f "tokens=1,*" %%A in ("!_ENV_VARS!") do (
    set "_TOKEN=%%A"
    set "_ENV_VARS=%%B"
    echo !_TOKEN! | findstr "=" >nul 2>&1
    if !errorlevel!==0 (
        for /f "tokens=1,* delims==" %%K in ("!_TOKEN!") do (
            set "_KEY=%%K"
            set "_VAL=%%L"
            if "!_VAL!"=="''" set "_VAL="
            echo set "!_KEY!=!_VAL!" >> "!_TMPFILE!"
        )
    )
)
goto parse_vars

:execute
if !_FOUND_SEMI!==1 (
    :trim_spaces
    if "!_COMMAND:~0,1!"==" " (
        set "_COMMAND=!_COMMAND:~1!"
        goto trim_spaces
    )
    if not "!_COMMAND!"=="" echo !_COMMAND! >> "!_TMPFILE!"
)

endlocal
call "!_TMPFILE!"
del "!_TMPFILE!" 2>nul

With this script, using the export command now works without errors while also setting the environment variables correctly.