anomalyco / anomalyco/opencode

OpenTUI fails to start on Windows ARM64: bun:ffi dlopen() is not available in this build

Open
#38,520 3 comments 2 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Jul 23, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

I'm unable to start the TUI on a Windows 11 ARM64 machine.

The CLI installs successfully via Winget and most commands work as expected, but any command that starts the terminal UI fails with the following error:

Failed to initialize OpenTUI render library: bun:ffi dlopen() is not available in this build (TinyCC is disabled)

Device: Microsoft Surface Laptop 7 Architecture: ARM64 OpenCode: 1.18.4 Installed via Winget (SST.opencode)

Interestingly:

  • opencode --help ✅ works
  • opencode --version ✅ works
  • opencode web ✅ works
  • opencode ❌ fails
  • opencode --mini ❌ fails

This looks like the ARM64 build is unable to initialize the native OpenTUI renderer.

Additional information

opencode web works correctly, so the CLI itself is functional.

The issue only occurs when initializing the terminal UI (OpenTUI).

Output:

Error: Unexpected error

Failed to initialize OpenTUI render library:
bun:ffi dlopen() is not available in this build (TinyCC is disabled)

Plugins

None

OpenCode version

1.18.4

Steps to reproduce
  1. Install OpenCode using Winget:

    winget install SST.opencode

  2. Open PowerShell.

  3. Verify installation:

    opencode --version

  4. Run:

    opencode

  5. The application immediately exits with:

    Failed to initialize OpenTUI render library:
    bun:ffi dlopen() is not available in this build (TinyCC is disabled)

Screenshot and/or share link

No response

Operating System

Windows 11 ARM64

Terminal

Windows PowerShell 7 (also reproducible in the VS Code integrated terminal)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.