dsh-backstage

Configuration

The plugin accepts optional configuration (in the config block of the patch line or a profile patch layer); everything has a default, and illegal values fail plugin loading rather than running half-configured:

- insert:
    - id: backstage
      name: dsh-backstage
      config:
        bufferCapacity: 20000   # output lines kept per job (100-200000, default 5000)
        defaultGroup: 'default' # default group tag when none is specified
        backend: 'auto'         # 'pty' (real pseudo-terminal) | 'pipe' (pipe fallback) | 'auto'
        stopGraceMs: 1500       # grace period for graceful stop, then force kill (50-60000)
        portScan: true          # check requested port occupancy before launch

backend semantics: pty uses node-pty (ConPTY on Windows) and interactive programs behave exactly as on a real terminal; pipe uses a plain subprocess pipe without terminal semantics (programs that only flush when a TTY is present may buffer output), with zero native dependencies; auto prefers pty and degrades to pipe when no native module is available.