Skip to content

v0.3.3 — Interactive Memory Inspector

Choose a tag to compare

@alertxsto alertxsto released this 10 Nov 05:59
· 55 commits to main since this release
4015d01

Interactive memory inspection for supported agent hosts, with explicit ownership, scoped access, and confirmed changes.

Native inspectors

  • OpenCode CLI and Desktop, pi, and omp provide native inspection on their verified host versions.
  • Hermes Desktop and its web dashboard provide separate native inspector integrations. The loopback browser companion is optional and must be launched explicitly.
  • The inspector includes scoped browsing, history, sharing permissions, maintenance previews, transfer, settings, and an offline deterministic summary.

Reliability and security

  • Inspector subprocesses resolve storage from the same trusted launcher environment as their native context. A conflicting launcher home is denied; config files cannot supply trusted inspector control channels.
  • An unavailable selected config no longer falls back to another store, and ~-prefixed SQLite paths resolve against the trusted process home before opening.
  • Malformed non-object responses from the companion's inspector subprocess return redacted unavailable or unknown_outcome results instead of dropping the request. Downloads retain their existing unavailable-or-revoked error.

Known limitations

  • OpenCode Web loads the server plugin but does not discover third-party GUI contributions. The companion is not a native Web plugin.
  • Hermes classic CLI and TUI do not provide the authenticated session and scope lifecycle required for a native visual inspector. Existing provider and command integrations remain available.
  • A source-workspace npm audit --omit=dev reported 26 moderate dependency entries involving upstream glob and minimatch advisories through OpenCode/OpenTUI dependencies. Exploitability in installed hosts has not been assessed.
  • Local installation on Node 24.19.0 warned that @opentui/core 0.7.0 declares Node 26.4.0 or Bun 1.3.14 as its minimum; the local build and native tests passed despite the warning.
  • All three npm packages now list 0.3.3, but their later publication used develop builds whose entry points differ from this tagged release's tarballs. Matching versions do not imply identical provenance. For Python 0.3.3, use the plugin tarballs attached to this release rather than the npm 0.3.3 builds. A coordinated new version is required to restore a single release source; existing registry versions will not be overwritten.

Installation and verification

The release workflow gates the Python package and downloadable plugin tarballs on native-package checks, the official Hermes SDK, and strict recall with the real default embedding model. Check PyPI and the assets on this release for actual availability; a successful source build alone is not publication.

See the support matrix for tested hosts and unresolved targets.