LLMSkillHub
mirroredCopied from vellum-ai/vellum-assistant under MIT. vellum-ai has not claimed this page, and is not affiliated with LLM SkillHub.

vellum-ai / vellum-terminal-sessions

Manage persistent tmux terminal sessions: create, read, write to, list, and close named shell sessions. For Claude Code or Codex, use the ACP skill instead.

0
SKILL.md
2.8 KB
⚠This file contains 1 character(s) that do not render as themselves (U+FE0F). They are shown highlighted below.

Overview

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

Sandbox ModeHost Mode
Where tmux runsIn the assistant's sandboxOn the user's host machine
How user connectsvellum terminal attach <session-name>User opens their own terminal
Assistant accessDirect (bash tool)Via host_bash
Best forLong-running builds, servers, always-on tasksWork 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