Repository navigation
Releases
Releases · elad12390/opencode-monitors
v0.3.2
Fixed
- Fresh OpenCode 2 installs could fail to resolve conflicting OpenTUI peers. The package now uses the host-provided OpenTUI runtime without declaring conflicting optional peers.
- Clarified that output delivered to an agent can be saved in OpenCode session history, even though the popup's output buffer stays in memory.
Added
- A package test exercises OpenCode's Bun/Arborist dependency resolver with the packed artifact.
- A demo of the popup and live monitor notifications, recorded in OpenCode with fictional log entries.
v0.3.1
Changed
- Releases are published from GitHub Actions with npm trusted publishing and provenance, so each version on npm can be traced to the commit and workflow that built it. 0.3.0 was published by hand.
- Re-running the release workflow for a version that is already on npm skips the publish and still creates the GitHub release.
v0.3.0
First release as opencode-monitors, a fork of opencode-sentinel 0.2.0.
Changed
- Renamed the package to
opencode-monitorsand the tools tomonitor,stop_monitorandlist_monitors.sentinel_pingandsentinel_spikeare gone. stop_monitortakes a monitor's description or its ID; an ambiguous or unknown name stops nothing and lists what is running.- Tool descriptions say what each tool does, why and when to use it, and how, in one paragraph each; results are plain sentences.
- The state file moved to
~/.local/state/opencode-monitors/monitors.json(OPENCODE_MONITORS_STATE_FILE). Commands also getMONITOR_SESSION_ID;SENTINEL_SESSION_IDis still set. - stderr is no longer written to
/tmp/sentinel-<id>-stderr.log. It stays in memory, shows in/monitors, and its last lines are quoted when a command fails.
Added
/monitorspopup (OpenCode 2): every monitor across projects with status, timing and line counts, its stdout and stderr, scrolling, kill with confirmation, and an All projects / This project filter.- The agent is told whenever a monitor ends: clean exit, failure, a kill from
/monitors, plugin unload, or an OpenCode restart or crash, with the command when a restart may be wanted. - Restart recovery: monitors left running by a crashed OpenCode are killed (after checking the process still runs that command) and their sessions are told.
- Test suites: integration (real processes, plugin copies, crashes),
/monitorsrendering, performance, and an npm package install test.
Fixed
- A catastrophic
filteroruntilregex froze OpenCode; patterns now run in a worker with a 250 ms limit per line. - A line with no newline grew memory without limit; lines are cut at 64K characters.
- After a flood or
untilstop, leftover output threw "Monitor not found" errors. - OpenCode loads one plugin copy per open project; the copies now share one monitor list, so
/monitorssees every monitor and one project's startup no longer kills another's monitors.