OpenCode++ continues to use the native OpenCode TUI on Windows. It does not build a Desktop replacement and does not embed the TUI in another terminal surface.
Use one of three input paths.
Use direct input for short prompts:
Fix the login timeout bug and add a regression test.This keeps the normal OpenCode TUI experience unchanged.
For long prompts, use OpenCode's editor flow:
opencode-plusplus setup-editor
opencode-plusplusOn Windows, setup-editor writes a user-level EDITOR environment variable. It chooses the first available editor in this order:
code --waitcursor --waitnotepad
Restart the terminal after running setup-editor, then open the editor from OpenCode TUI with /editor or Ctrl+X E.
On non-Windows platforms, setup-editor prints an export EDITOR="..." line for your shell profile instead of changing the environment.
Use /clip when you want to move a large prompt through the system clipboard without fighting terminal paste behavior.
Install the slash command once per repository:
opencode-plusplus install-commandsCopy your long prompt, then write it into the OpenCode++ clipboard file:
opencode-plusplus clipOr pipe text directly:
Get-Content .\prompt.md -Raw | opencode-plusplus clipThe payload is written to:
.opencode-plusplus/clipboard/latest.mdThen open OpenCode TUI and run:
/clipThe slash command asks OpenCode to read .opencode-plusplus/clipboard/latest.md as the long-form user input.
.opencode-plusplus/clipboard/is ignored by git.opencode-plusplus tuiprints a Windows hint whenEDITORis not set: use/editororCtrl+X Efor long text.opencode-plusplus clipis a helper around the native TUI; it does not modify OpenCode source code.