Skip to content

v0.1.1-beta.4: Selectable libghostty-vt renderer backend

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Apr 09:29
· 52 commits to main since this release
v0.1.1-beta.4
704ae9d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This beta adds a selectable semantic renderer backend so snapshot, wait, and getVisibleText can run against either the existing ghostty-web Playwright pipeline or the new native libghostty-vt addon. PNG screenshots and WebM exports continue to use ghostty-web, and artifact metadata honestly reports the actual producer. The release also clarifies skill discovery in --help, declares an explicit Apache-2.0 license, and restructures the user-facing documentation.

Highlights

  • New --renderer <ghostty-web|libghostty-vt> flag (plus AGENT_TTY_RENDERER env var and defaultRenderer config key) for per-command renderer selection.
  • Optional @coder/libghostty-vt-node native addon, loaded lazily and only when explicitly selected.
  • Apache-2.0 license is now declared in the repo and in package.json metadata.

Added

  • Selectable libghostty-vt renderer backend (#42) by @ThomasK33. Adds @coder/libghostty-vt-node@0.1.0-beta.0 as an optionalDependency and wires a renderer registry through the host RPC, offline replay, and CLI commands.

    • Selection precedence: CLI flag → env var → config → ghostty-web (default).
    • Unknown renderer names fail fast before any backend is constructed.
    • Missing native addon produces an actionable error pointing at --renderer ghostty-web as recovery.
    • libghostty-vt is semantic-only in v1: screenshot and record export --format webm transparently fall back to ghostty-web, and rendererBackend in artifact metadata reports the actual producer (so a screenshot requested with --renderer libghostty-vt still reports ghostty-web).
    # Per-command selection
agent-tty --renderer libghostty-vt snapshot <session-id> --json
agent-tty --renderer libghostty-vt wait <session-id> --text "READY>" --json

# Or as a default
export AGENT_TTY_RENDERER=libghostty-vt

  • Skills-discoverability help footer (#38) by @ThomasK33. The top-level --help outro now reads: "Coding agents: after loading the core agent-tty skill, run agent-tty skills list to discover other bundled skills and agent-tty skills get <name> to load one."

  • Apache-2.0 LICENSE (#43) by @ThomasK33. The repository now ships an Apache-2.0 LICENSE file at the root and declares "license": "Apache-2.0" in package.json, so consumers and automation can detect the package license from npm metadata.

Changed

  • Documentation restructure (#41) by @ThomasK33. The root README is now a product-facing entry point (what agent-tty is, why it exists, quickstart, common usage, limitations, roadmap, license), with detailed material moved into focused docs for installation, usage, agent skills, and troubleshooting. As part of this pass, the doctor --json home-isolation diagnostic message was updated from the stale Agent-terminal name to agent-tty.

Notes

  • libghostty-vt is opt-in and its native addon is an optionalDependency. Default users on any platform are unaffected and never load the native code.
  • PNG screenshots and WebM exports continue to require the ghostty-web (Playwright) path even when --renderer libghostty-vt is selected.

Full Changelog: v0.1.1-beta.3...v0.1.1-beta.4

Install from npm once the trusted publish job for this workflow completes:

npm install -g "agent-tty@0.1.1-beta.4"
agent-tty version --json

If you need a registry-independent fallback, install the verified tarball asset from this release directly:

VERSION=0.1.1-beta.4
RELEASE_TAG=v0.1.1-beta.4
TARBALL_URL=https://github.com/coder/agent-tty/releases/download/v0.1.1-beta.4/agent-tty-0.1.1-beta.4.tgz

npm install -g "$TARBALL_URL"
agent-tty version --json

For private releases or environments that require authenticated downloads, fetch the asset first and then install locally:

gh release download "v0.1.1-beta.4" --repo "coder/agent-tty" --pattern "agent-tty-0.1.1-beta.4.tgz"
npm install -g "./agent-tty-0.1.1-beta.4.tgz"
agent-tty version --json

SHA-256 checksum: d987cdf1b4bc6af0b97033eb23d229f37c08f36dc39bba9fe7ccec2f4bf99bf6 (see agent-tty-0.1.1-beta.4.tgz.sha256 for the portable checksum file).

This workflow prepares one verified tarball and reuses it across GitHub Release assets and npm publishing instead of rebuilding it.

Contributors

ThomasK33
Assets 4
Loading