OpenParable
Skip to content
← Back to skills

Vellum Terminal Sessions

Apps & Automation
vellum-terminal-sessions

Vellum Terminal Sessions is an Agent Skill for apps & automation published in the vellum-ai/vellum-assistant repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vellum-ai/vellum-assistant/blob/HEAD/skills/vellum-terminal-sessions/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vellum-terminal-sessions, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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 forClaude Code orchestration, 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 · host-sessions.md · 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.

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