Scoop-fixes-opencode-windows-x64-garbled-output-issue-but-cause-unknown #10341

Question

System Environment

• Windows 10 x64_22h2

Initial Problem Discovery

Direct Download from GitHub Release

https://github.com/anomalyco/opencode/releases/download/v1.1.34/opencode-windows-x64.zip

Extracted to Installation Directory and Added to env.PATH

Example: "D:\SoftwareWorkspace\opencode_x64\opencode.exe"

Launched via opencode Command in Windows Terminal or by Double-clicking opencode.exe

Result: After launch, all input becomes uncontrolled and displays garbled text. Even mouse movements generate massive amounts of garbled output, making normal usage impossible.

Installing opencode-windows-x64 via Scoop Resolves This Issue

scoop install opencode

After installation via Scoop, the application works correctly.

Strange Phenomena Discovered While Investigating Why Scoop Fixes the Problem

According to Scoop's Bucket Metadata, It Uses the Same Download Link

// ~\scoop\buckets\main\bucket\opencode.json
{
    "version": "1.1.34",
    "description": "The open source AI coding agent.",
    "homepage": "https://opencode.ai/",
    "license": "MIT",
    "architecture": {
        "64bit": {
            "url": "https://github.com/anomalyco/opencode/releases/download/v1.1.34/opencode-windows-x64.zip",
            "hash": "2ecf5682187714057cd51c178ae29687672a2bd753a919d3d1d49591d23a1fec"
        }
    },
    "bin": "opencode.exe",
    "checkver": {
        "github": "https://github.com/anomalyco/opencode"
    },
    "autoupdate": {
        "architecture": {
            "64bit": {
                "url": "https://github.com/anomalyco/opencode/releases/download/v$version/opencode-windows-x64.zip"
            }
        }
    }
}

So Why Does Scoop Installation Work While Browser Download + Extract Fails?

I located the Scoop-installed program path:

# scoop shims link
~\scoop\shims\opencode.exe
# link to real exe file
~\scoop\apps\opencode\1.1.34\opencode.exe

Test 1: Copy Scoop-Installed Program and Run Outside

When copied to the same location (e.g., C: drive root) and executed directly, the garbled output bug reappears.

cp "~\scoop\apps\opencode\1.1.34\opencode.exe" "C:\opencode.exe"
# execute outside of scoop
. "C:\opencode.exe"

Test 2: Copy Originally Broken File to Scoop Directory

When I copy the original problematic file into any location within the Scoop directory, the problem disappears and no garbled output occurs.
BugFixed Only When ExeFile in Scoop Folder to Run:I wonder How?
Conclusion: This is not a file difference issue.

The Core Question: What Exactly Does Scoop Do?

Why does simply copying the file into the Scoop directory fix the problem?

I tested scoop shim add with the external exe file, but the garbled output issue persists. So it's not the shim mechanism—there must be something about copying the file into the Scoop directory that triggers the fix.

I want to understand what processing Scoop does during installation that resolves this wrapper issue.