vellum-terminal-sessions

$npx mdskill add vellum-ai/vellum-assistant/vellum-terminal-sessions

Manage persistent terminal sessions via tmux in sandbox mode and host mode

  • User asks about their running terminal sessions or processes.
  • Depends on tmux for session management in host mode.
  • Decides actions based on user input and needs, such as creating, reading, writing to, listing, and closing sessions.
  • Delivers results through interactive commands and notifications.

SKILL.md

.github/skills/vellum-terminal-sessionsView on GitHub ↗
---
name: vellum-terminal-sessions
description: Manage persistent terminal sessions via tmux. Create, read, write to, list, and close named shell sessions. Use when the user asks about running terminal processes, wants help orchestrating CLI tasks, or asks you to monitor or interact with long-running commands. Also use when the user mentions tmux sessions.
compatibility: "Sandbox mode works without any host dependencies. Host mode requires tmux installed on the user's machine. Works on macOS and Linux."
metadata:
  emoji: "🖥️"
  author: vellum-ai
  version: "0.2"
  vellum:
    category: "system"
    display-name: "Terminal Sessions"
    activation-hints:
      - "User asks about their running terminal sessions or processes"
      - "User wants to monitor a long-running command"
      - "User wants the assistant to run something in a persistent shell"
      - "User mentions tmux or terminal management"
      - "User wants to orchestrate multiple CLI agents (e.g. Claude Code sessions)"
    avoid-when:
      - "A simple one-shot command that host_bash handles fine"
      - "The user is asking about shell scripting in general, not session management"
---

## Overview

This skill manages **persistent terminal sessions** via tmux. Two modes:

|                       | Sandbox Mode                               | Host Mode                                                           |
| --------------------- | ------------------------------------------ | ------------------------------------------------------------------- |
| **Where tmux runs**   | In the assistant's sandbox                 | On the user's host machine                                          |
| **How user connects** | `vellum terminal attach <session-name>`    | User opens their own terminal                                       |
| **Assistant access**  | Direct (`bash` tool)                       | Via `host_bash`                                                     |
| **Best for**          | Claude Code orchestration, always-on tasks | Work needing host access (e.g. SwiftUI builds, host-local services) |

**Default:** Use **Sandbox Mode** unless the task specifically requires host access. Details: [sandbox-sessions.md](references/sandbox-sessions.md) · [host-sessions.md](references/host-sessions.md) · [tmux-best-practices.md](references/tmux-best-practices.md)

## Prerequisites

**Sandbox Mode:** No setup needed — tmux is available in the sandbox.

**Host Mode:** Requires tmux on the host — see [host-sessions.md](references/host-sessions.md).

## Workflow: Orchestrating Multiple Sessions

- **List** all sessions: `tmux list-sessions` to get names and current commands
- **Read** each: `tmux capture-pane -t NAME -p -S -50` (30-50 lines is usually enough)
- **Summarize** before acting: "Build done, tests at 73%, deploy waiting for confirmation"
- **Act** on the user's instructions

More from vellum-ai/vellum-assistant

SkillDescription
acpSpawn external coding agents via the Agent Client Protocol (ACP)
amazonShop on Amazon and Amazon Fresh through your browser
api-mappingRecord and analyze API surfaces of web services
app-builderBuild and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use, or to edit an app they already built here. Do NOT reach for a ui_show dynamic_page to fake an artifact — build a real persistent app here. NOT for complex, multi-user, or shippable products — those go to a real project folder with a coding agent (see Scope below).
app-controlDrive a specific named macOS app via raw input bypassing the Accessibility tree
assistant-migrationMigrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum primitives. Handles single-source and multi-source migrations with a unified, deduplicated inventory.
chatgpt-importImport conversation history from ChatGPT into Vellum
cli-discoverDiscover which CLI tools are installed, their versions, and authentication status
contactsManage contacts, communication channels, access control, and invite links
conversation-launcherOffer the user several spin-off conversations as clickable buttons on a single persistent card. Each click spawns a fresh seeded conversation in the sidebar; the user keeps their place in the current conversation. Use when you want to branch into N focused threads (research directions, draft choices, pending replies, triage of N items) without losing the current context. Not for single-destination pivots — just reply inline.