Skip to content

OpenCode CLI Critical Runtime Failure #7960

Closed as not planned
Closed as not planned

Description

@arnabclir

Description

Files:

opencode-installation-issue-report.md
opencode-fix-documentation.md
Summary: OpenCode v1.1.13 installation appears successful but the tool is completely non-functional due to Bun runtime virtual filesystem (bunfs) incompatibility with PRoot environments.

Key Issues:

UX Issue: Installation script doesn't update current shell PATH (easily worked around with source ~/.bashrc)
Critical Bug: Bun's bunfs cannot resolve module paths in PRoot, causing all core commands to fail
Error:

Error: Cannot find module '/home/arnab/.cache/opencode/node_modules/opencode-copilot-auth'
from '/$bunfs/root/src/index.js'
Working Commands: --version, --help, models, debug paths Broken Commands: run, stats, debug config (anything that loads plugins)

Severity: CRITICAL - Tool is completely unusable on this platform

Root Cause: Bun's virtual filesystem (bunfs) is incompatible with PRoot's user-space virtualization layer

Recommended Fixes:

Detect PRoot/container environments and use Node.js runtime instead of Bun
Disable bunfs via BUN_DISABLE_BUNFS=1 environment variable
Use absolute filesystem paths instead of Bun virtual paths
Add platform compatibility warnings at install time
Status: No user workaround available - Requires OpenCode team to implement PRoot compatibility

Plugins

No response

OpenCode version

No response

Steps to reproduce

  1. Just installed OpenCode

Screenshot and/or share link

No response

Operating System

proot distro in termux

Terminal

Termux

Activity

  1. github-actions commented on Jan 12, 2026

    @github-actions
    Contributor

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

    Feel free to ignore if your specific case differs from these, but these issues address Bun runtime and Proot/Termux compatibility concerns.

  2. thdxr commented on Mar 25, 2026

    @thdxr
    Member

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

  3. removed
    bugSomething isn't working
    on May 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions