@renai-labs/ren-tui-plugin
v0.0.2
Published
Ren TUI plugin for opencode — attribution, command lockdown, and in-TUI Ren navigation. Active only inside a Ren attach.
Maintainers
Readme
@renai-labs/ren-tui-plugin
The Ren TUI plugin for opencode. It adds Ren behavior —
turn attribution/billing, command lockdown, and in-TUI Ren navigation — only
when the current process is a Ren attach. For any other opencode session it is
a guaranteed no-op: with the plugin installed globally, plain opencode behaves
exactly as if it were not installed (plan §3.5, the activation gate).
Install
Run ren tui install (wires the plugin — and opencode itself — into your global
opencode.json), or add it to the plugin array by hand:
{
"plugin": ["@renai-labs/[email protected]"]
}Launch
The Ren CLI is the launcher — there is no standalone bin:
ren tui # interactive pod → project → session picker, then attach
ren tui attach <id> # attach directly to a sessionHow it works
The plugin sits behind a single activation gate. ren tui / ren tui attach
spawn opencode attach <url> with REN_ATTACH=1 and the session/pod/project
context in the environment (never credentials — those come from your Ren profile
file). Inside the TUI, the plugin checks the gate first and returns early for any
non-Ren session.
Versioning
The plugin is pinned to a specific opencode plugin API (@opencode-ai/plugin/tui)
via the repo-root .opencode-version — the same version the Ren sandbox fork
ships and that ren tui expects. bun run sync-opencode-version keeps the pin in
lockstep, and prepublishOnly fails on drift so a published build always matches
its target opencode.
