Extensions

Extensions are server-side Node packages that add capabilities to Terminay through a versioned API, @terminay/extension-api. The current API version is 3.7.

Contribution types

An extension declares one or more of these in its manifest and registers a runtime for each during activation.

ContributionWhat it doesPermissionReference
Agent session source
agentSessionSources
Reports the live coding-agent sessions of its harnesses on the server's machine. agent-observation Agent session sources
MCP install target
mcpInstallTargets
Writes, checks, and removes the Terminay MCP server registration in one client's configuration. mcp-registration MCP install targets
Chat provider
agentChatProviders
Runs the turns of an agent chat Terminay owns, such as Pixel, through the user's installed agent. agent-chat Chat providers
Terminal launcher
terminalLaunchers
Adds a button to every folder's New terminal row that starts an installed program. agent-launch Terminal launchers
Terminal command default
terminalCommandDefaults
Adds flags in front of a command typed in a Terminay terminal, or sets environment on the terminal's shell. terminal-command-defaults Terminal command defaults
Bot agent
botAgents
Makes a coding agent available to Terminay Bots, with its image install and sign-in. agent-bots Bot agents
Language server
languageServers
Tells Terminay how to launch a language server for a set of languages and file extensions. None Language servers
Worktree insight source
worktreeInsights
Publishes a pull request and CI checks for each Git worktree of an open project. worktree-observation Worktree insights
Forge source
forgeSources
Answers queries for the pull requests and issues on a forge's accounts, for Terminay's Pull Requests and Issues lists. forge-source Forge sources

Themes, editor plugins, commands, renderer components, and custom protocol operations are not supported contribution kinds.

How an extension runs

  1. You publish or pack a standard npm package with a terminay manifest in package.json.
  2. An administrator installs it on the selected Terminay Server from Settings → Extensions.
  3. Terminay validates the manifest, starts the package in its own Node process, and calls activate(context).
  4. The extension registers a runtime for each contribution its manifest declares.

Terminay owns the UI, navigation, ordering, and canonical state. An extension supplies bounded facts and never loads code into a client.

Bundled extensions

Terminay ships four official extensions built on the same public API, with no private access. They are useful as reference implementations.

Extension IDContributes
com.terminay.builtin-agentsOne session source for Claude Code, Codex, Grok, and oh-my-pi; six MCP install targets; Claude Code and Codex chat providers, terminal launchers, and bot agents; and two command defaults: codex --no-daemon and CLAUDE_CODE_DISABLE_AGENT_VIEW=1 for claude.
com.terminay.language.typescriptA TypeScript and JavaScript language server.
com.terminay.giteaA worktree insight source for Gitea pull requests and commit statuses, and a forge source for Gitea pull requests and issues.
com.terminay.githubA worktree insight source for GitHub pull requests and checks, and a forge source for GitHub pull requests and issues.

Next steps