Vellum Terminal Sessions
Apps & Automationvellum-terminal-sessionsVellum 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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
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 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 · 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-sessionsto 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