Terminals

A portable terminal panel built as a Svelte SPA on top of xterm.js. It streams read-only command output and runs fully interactive PTY shells — TUI-capable — in the browser. The same definition runs standalone, mounts into a Vite host, or docks inside a hub.

Package: @devframes/plugin-terminals · framework: Svelte + xterm.js

What it does

• Read-only output — stream the output of a command into a terminal view via devframe's streaming channels.
• Interactive shells — spawn PTY-backed sessions you can type into, including full-screen TUI programs. Sessions can be renamed, resized, restarted, and removed; the session list lives in shared state so every panel stays in sync.
• Presets — declare named commands the user can launch with one click.

Interactive shells run on a real pseudo-terminal via zigpty's prebuilt native bindings (Linux/macOS/Windows, x64/arm64, no install scripts). Where the bindings can't load, sessions degrade to pipe-based terminal emulation.

Standalone

npx @devframes/plugin-terminals

Mount into a Vite host

// vite.config.ts
import { terminalsVite } from '@devframes/plugin-terminals/vite'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    terminalsVite(),
  ],
})

Programmatic

createTerminalsDevframe(options) returns a definition you can deploy through any adapter. Declare presets to seed the launcher:

import { createTerminalsDevframe } from '@devframes/plugin-terminals'

export default createTerminalsDevframe({
  presets: [
    { id: 'dev', title: 'pnpm dev', command: 'pnpm', args: ['dev'] },
  ],
})

Hub aggregation

Mounted into a hub, the plugin owns PTY/child-process spawning and its own streaming channel (devframes-plugin-terminals:output) — that's what the panel renders. It also mirrors every session it spawns into ctx.terminals (the hub's aggregate registry, streaming on devframe:terminals) so other tools — a launcher dock, a custom panel — see the same session list without depending on the plugin's own types. A session started the other way, via ctx.terminals.startChildProcess / startPtySession directly (e.g. from a launcher dock), shows up in the terminals panel too — the plugin reads foreign hub sessions read-only and renders them alongside its own, subscribing to the hub's channel for their output.

ctx.terminals is the source of truth for "what sessions exist"; the plugin is the panel that renders them and the one PTY-capable provider among possibly several session sources. The plugin never imports @devframes/hub's types to stay mountable without a hub — it duck-types the minimal register / update / events shape it needs.

Source

plugins/terminals