[FEATURE]: Portable wrapper scripts for running OpenCode without global installation

[jek-bao-choo]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

It would be useful to have official portable wrapper scripts that let users run OpenCode without requiring a global install, modifying PATH, or writing any files to the home directory.

Currently, to use OpenCode you need to install it globally. This isn't always desirable — for example when evaluating the tool on a shared machine, running it in a locked-down corporate environment, keeping
project tooling self-contained, or using it in CI/ephemeral environments where you don't want to pollute the system.

A portable wrapper would:

• Download the correct OpenCode binary for the current platform and architecture automatically
• Keep everything (binary, config, data, cache, state) in a single .opencode_portable/ directory next to the script
• Isolate all state via XDG environment variables so nothing touches ~/.config, ~/.local, etc.
• Support version pinning via an environment variable or .opencode-version file
• Provide flags for forced update, version check, and help
• Auto-detect platform details: macOS ARM64/x64 (including Rosetta), Linux glibc/musl, AVX2/baseline, and Windows x64

Ideally this would include:

• A Bash script (opencode-portable.sh) for macOS and Linux
• A PowerShell script (opencode-portable.ps1) for Windows
• A guide explaining prerequisites, download instructions, usage, version pinning, plugin/skill installation, and troubleshooting

[VoxCodice]

I’d go one step further and support a local config file that OpenCode reads at startup and uses to determine the locations of its config/data/cache/state directories. In my environment (workstations that revert to a clean snapshot), I don’t want to constantly set environment variables. If OpenCode simply prioritized a config file located next to the executable (or in the portable directory), then I wouldn’t need a separate .sh or .ps1 wrapper at all.

This would also work great from a USB/pendrive: you could plug it into any machine, run OpenCode, and keep all state on the drive without changing anything on the host system.

If automatically reading a config file next to the executable is a concern (e.g., for security or unexpected behavior), an alternative would be to provide a flag like --config (or --portable) to enable this mode.

[colinandres885-boop]

https://www.govinfo.gov/link/bills/118/s/2438?billversion=mostrecent&link-type=pdf

[VoxCodice]

https://www.govinfo.gov/link/bills/118/s/2438?billversion=mostrecent&link-type=pdf

Not sure what this means. Pasted the wrong link perhaps?