Skip to content

Releases

v0.1.5 — fix: exact compose matching, verified panels

Choose a tag to compare

@angeloper86 angeloper86 released this 09 Oct 03:20

Full Changelog: v0.1.4...v0.1.5

v0.1.4 — docs: acme fixtures in the workspace example

Choose a tag to compare

@angeloper86 angeloper86 released this 02 Oct 01:06

Docs — the workspace example now uses the demo's acme fixtures. The rundev.workspace.json sample in
the README (acme-api, acme-web, acme-app) and the cwd JSDoc in src/manifest.ts now match the
throwaway workspace behind the screenshots and docs/demo.tape, so the docs and the demo tell the same
story. No functional changes.

Upgrade

opencode service restart   # re-resolves opencode-rundev@latest

v0.1.3 — one panel per app

Choose a tag to compare

@angeloper86 angeloper86 released this 30 Sep 02:46

Fix — a workspace up opened two panels. The TUI picker dispatched every rundev command twice:
session.command resolves to void, so the guard res !== undefined never returned and the CLI
fallback always fired as well. One picker confirmation ran the verb twice — two flutter run splits
typed into the focused terminal, 3s apart (the server event log shows two up: app runs from a single
select event). The guard now checks that the client exposes the method, and the CLI path stays as
the fallback for an unreachable server.

Fix — interactive services were never idempotent. statusOf promised to report a panel as
running when a record existed, but nothing ever wrote one (the pidfile is only written for process),
so every up reported unknown and relaunched the panel. rundev now records the panel it opens and
down forgets it:

  • a second up reports already instead of opening a duplicate panel;
  • up <svc> --force relaunches on purpose (also exposed as a force in the agent tool), and an
    explicit app@ios over an android panel retargets instead of answering already;
  • check — or targets.<t>.check, for a service that switches device — makes a panel verifiable:
    a closed app is detected and up relaunches by itself;
  • the marker lives in its own file (<name>.panel.json): stopProcess kills by pidfile, and pid: 0
    would have addressed the whole process group. A defensive pid guard covers that path too;
  • logs for an interactive service no longer claims "no log yet": the panel owns its output.

12 new smoke assertions cover the marker, --force, the retarget, the .env guard and the per-target
check. Prefer a verifiable setup when you write a manifest:

"app": {
  "kind": "interactive",
  "targets": {
    "android": { "device": "emulator", "envSection": "ANDROID", "requires": ["emulator"],
                 "check": "adb shell pidof com.example.app" }
  }
}

Upgrade

opencode service restart   # re-resolves opencode-rundev@latest

v0.1.2 — one /rundev command

Choose a tag to compare

@angeloper86 angeloper86 released this 29 Sep 04:41

Fix — /rundev was registered twice: by the server plugin (ctx.command.transform) and by the TUI
plugin as a client slash command (palette + slash). OpenCode lists server commands and client slash
commands in the same completion surface with no dedupe, so the palette showed two identical /rundev
rows with nothing to tell them apart.

There is now a single command surface. The TUI no longer registers a command: at a workspace root the
server command emits a select event (verb, workspace, members, sessionID) and the TUI opens
the existing checkbox picker from it, then re-dispatches the chosen members to the server command.
Clients without a TUI still get the text menu as fallback.

Upgrade

opencode service restart   # re-resolves opencode-rundev@latest

v0.1.1 — fix: TUI entrypoint deps

Choose a tag to compare

@angeloper86 angeloper86 released this 28 Sep 23:57

Fix — the TUI entrypoint (src/tui.tsx) needs @opentui/solid (JSX runtime) and solid-js, which were
declared as optional peer dependencies. Optional peers are not installed by npm, so loading the plugin
from the npm cache failed with:

Cannot find package '@opentui/solid' imported from .../opencode-rundev/src/tui.tsx

They are now regular dependencies (plus @opentui/core), verified by installing the published tarball
into a clean prefix and resolving them from the plugin file itself.

Upgrade

opencode service restart   # re-resolves opencode-rundev@latest

v0.1.0 — Run & Debug for the terminal-first world

Choose a tag to compare

@angeloper86 angeloper86 released this 28 Sep 22:12

First public release of opencode-rundev.

What it does — brings a repo's dev environment up and down from OpenCode with a deterministic
engine and no LLM in the loop: compose, process, browser, interactive, emulator and
simulator services, declared per repo in .opencode/rundev.json.

  • /rundev init [--guided] [free text] · status · up · down · logs · doctor · env · uninstall
  • Agent tools: rundev_status, rundev_up, rundev_down, rundev_logs, rundev_scan, rundev_apply
    plus the rundev-manifest skill.
  • Live sidebar (one block per repo in workspace mode), checkbox picker for workspace members, reports
    mirrored into the transcript as shell messages.
  • House rules: idempotent non-blocking up, down only stops what rundev started, .env is only
    verified, nothing destructive.

Install

// opencode.json(c)
{ "plugins": ["opencode-rundev"] }
npm i opencode-rundev   # or let OpenCode resolve it from the plugins list

Requires OpenCode ≥ 2.0 on macOS (the terminal panel strategy targets Ghostty; elsewhere it falls back
to the clipboard or a new window).