[Bug]: non-interactive-env still hardcodes Unix export prefix on Windows in v3.10.0

[Brisbanehuang]

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

This appears to be a regression / incomplete fix of the previously closed Windows shell compatibility issue.

On Windows, non-interactive-env still prepends a Unix-style export ...; prefix to git commands in v3.10.0, which breaks execution in cmd.exe and PowerShell.

The previous issue #566 was closed, but the current v3.10.0 build still contains a hardcoded Unix shell type in the compiled hook implementation.

Steps to Reproduce

1. Install the latest package:

   npm install -g oh-my-opencode@3.10.0

2. Use OpenCode on Windows with oh-my-opencode enabled.
3. Execute a git command through the bash tool, for example git status.
4. Observe that the command is rewritten with a Unix-style prefix:

   export CI=true DEBIAN_FRONTEND=noninteractive GIT_TERMINAL_PROMPT=0 ...; git status
   

5. In Windows shells this fails with:

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

Expected Behavior

The hook should either:

• detect the actual shell and emit shell-appropriate syntax, or
• avoid prepending Unix syntax on Windows entirely, or
• only run when the environment is truly non-interactive.

Actual Behavior

non-interactive-env still prepends a Unix export ...; prefix on Windows in the latest release.

Evidence

Local verification after upgrading to 3.10.0:

• Installed package version:

  • C:\Users\hacke\AppData\Roaming\npm\node_modules\oh-my-opencode\package.json
  • "version": "3.10.0"

• Compiled hook implementation still contains:

  • C:\Users\hacke\AppData\Roaming\npm\node_modules\oh-my-opencode\dist\index.js:40242
  • const envPrefix = buildEnvPrefix(NON_INTERACTIVE_ENV, "unix");

• The shell-aware helper still exists in the same build:

  • C:\Users\hacke\AppData\Roaming\npm\node_modules\oh-my-opencode\dist\index.js:17322
  • function buildEnvPrefix(env, shellType) { ... }
  • with explicit branches for unix, powershell, and cmd

So the issue is not that shell-specific support is missing globally; it is that this hook still forces "unix".

Workaround

Disabling the hook avoids the problem:

{
  "disabled_hooks": ["non-interactive-env"]
}

Additional Context

Related previously closed issue: #566

This new report is specifically about the latest release (v3.10.0) still shipping code that hardcodes Unix behavior in the Windows path.

Operating System

Windows

OpenCode Version

opencode-ai 1.2.20

[MarsGao]

I can also reproduce this on Windows, and I confirmed the same root cause from a local installed build.

Environment

• Windows 11
• OpenCode: opencode-ai 1.2.20
• oh-my-opencode plugin package seen locally: 3.8.5

Reproduction behavior

When agent runs git commands, command is rewritten like:

export CI=true DEBIAN_FRONTEND=noninteractive GIT_TERMINAL_PROMPT=0 GCM_INTERACTIVE=never HOMEBREW_NO_AUTO_UPDATE=1 GIT_EDITOR=: EDITOR=: VISUAL='' GIT_SEQUENCE_EDITOR=: GIT_MERGE_AUTOEDIT=no GIT_PAGER=cat PAGER=cat npm_config_yes=true PIP_NO_INPUT=1 YARN_ENABLE_IMMUTABLE_INSTALLS=false; git log --oneline --graph --all -20 --decorate

On Windows shell this fails with:

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

It may get retried multiple times in the same run.

Local evidence (compiled bundle)

• dist/index.js contains the non-interactive env map (NON_INTERACTIVE_ENV).
• In createNonInteractiveEnvHook, it still forces:

const envPrefix = buildEnvPrefix(NON_INTERACTIVE_ENV, "unix");

• buildEnvPrefix(env, shellType) already has unix / powershell / cmd branches, so this appears to be a forced-shell bug at hook call site.

Immediate workaround

Disable this hook in ~/.config/opencode/oh-my-opencode.json:

{
  "disabled_hooks": ["non-interactive-env"]
}

Thanks for investigating this regression.