Extensions

Extensions are server-side Node packages that add capabilities to Terminay through a stable, versioned API. Today they can provide project environments and coding-agent integrations; future capabilities will use the same package, permission, and runtime model.

Choose what to build

Agent quickstart

Build one current contribution type from package to installation.

Extension anatomy

Understand the manifest, entrypoint, contribution, and runtime boundary.

Two contribution types

Build thisWhen it fitsStart with
Agent provider Read a known agent’s terminal-scoped journal and publish its turns, tools, waits, and subagents. Agent guides
Project-environment provider Connect a project to infrastructure such as an SSH host, VM, or managed workspace. Environment guides

How an extension runs

  1. You publish or pack a standard npm package with a terminay manifest.
  2. An administrator installs it on the selected Terminay Server.
  3. Terminay validates the manifest, starts the package in its own Node process, and calls activate().
  4. Your extension registers only the contributions declared in its manifest.

Terminay owns the UI and the canonical agent state. An extension supplies declarative data, uses scoped host brokers, and never loads renderer code.

Next steps