Execute git operations using cmd /c on windows fails #11288

Activity

1. pjhool

   added

   bugSomething isn't workingSomething isn't working

   on Jan 30, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 30, 2026
3. github-actions

   added

   windows

   on Jan 30, 2026
4. github-actions commented on Jan 30, 2026

   

   github-actionsBot

   on Jan 30, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of or related to existing issues. Please check:

   • Windows Support #631: Windows Support (umbrella issue for all Windows-related problems)
   • Windows: Git Bash auto-detection derives invalid bash.exe path #10871: Git Bash auto-detection on Windows
   • Bash Fork Issues - Investigation Included #6488: Bash Fork Issues on Windows
   • Ctrl-C doesn't clear the input on Windows, it crashes #10538: Ctrl-C crashes on Windows (similar shell handling issue)
   • Terminal state not restored when exiting with ctrl+c on windows (git bash) #10719: Terminal state not restored when exiting with ctrl+c on Windows

   Root Cause: The error message 'export is not recognized as an internal or external command' indicates that bash shell syntax is being executed in Windows cmd.exe, which doesn't support the 'export' command. This is a shell mismatch issue where bash commands are being sent to cmd.exe instead of being properly executed in a bash shell.

   Feel free to ignore if none of these address your specific case, but checking #631 (the Windows support umbrella) and #10871 (bash auto-detection) would be most relevant.
5. DaveW001 commented on Jan 30, 2026

   

   DaveW001

   on Jan 30, 2026

   More actions

   Reproduced this behavior with a slightly different signature affecting PowerShell.

   Additional Symptoms:

   • Shell: PowerShell
   • Error: CommandNotFoundException on the = token (caused by VAR=val syntax).
   • Artifacts: Creation of a file named nul in the working directory (caused by > /dev/null redirection failing in Windows).

   This confirms the issue affects both CMD (reporting export error) and PowerShell (reporting = error).

   Likely caused by #10871 (failed Bash detection) causing fallback to native Windows shells while passing Bash-specific syntax.
6. xq114 commented on Feb 22, 2026

   

   xq114

   on Feb 22, 2026

   More actions

   I workaround it by disabling hook non-interactive-env in oh-my-opencode.json:

   {
     "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/master/assets/oh-my-opencode.schema.json",
     "disabled_hooks": ["non-interactive-env"]
   }
   

   👍React with 👍3Reacted by Frans Hanjaya, yarkylz and aniya

   ❤️React with ❤️1Reacted by aniya
7. franshjy commented on Mar 3, 2026

   

   franshjy

   on Mar 3, 2026

   More actions

   I workaround it by disabling hook non-interactive-env in oh-my-opencode.json:

   {
     "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/master/assets/oh-my-opencode.schema.json",
     "disabled_hooks": ["non-interactive-env"]
   }
   

   Can vouch for this, although not sure perhaps this might me an omo issue?
8. BeanYa commented on Mar 24, 2026

   

   BeanYa

   on Mar 24, 2026

   More actions

   I ran commands and opencode just got a death loop on running 'export' while I was working on Windows Powershell.

   This works for me:

   I workaround it by disabling hook non-interactive-env in oh-my-opencode.json:我通过在 oh-my-opencode.json 中禁用钩子 non-interactive-env 来解决这个问题：

   {
     "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/master/assets/oh-my-opencode.schema.json",
     "disabled_hooks": ["non-interactive-env"]
   }
   
9. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   windows

   on May 3, 2026
10. github-actions commented on Jul 3, 2026

    

    github-actionsBot

    on Jul 3, 2026 – with GitHub Actions

    Contributor

    More actions

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
11. github-actions

    closed this as not plannedon Jul 3, 2026