vellum-terminal-sessions

Manage persistent tmux terminal sessions for long-running CLI tasks.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill vellum-terminal-sessions-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vellum-terminal-sessions
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/vellum-terminal-sessions
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill vellum-terminal-sessions-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you reliably create and manage persistent terminal sessions so long-running commands don’t get lost and you can monitor progress across turns or from different terminals.

Core Features & Use Cases

  • Persistent tmux session management: Create, list, read output from, write/send commands to, and close named shell sessions.
  • Sandbox vs host operation: Run sessions inside the assistant sandbox by default, or use tmux on your host via host_bash when real host tooling/services are required.
  • Practical monitoring for ongoing work: Capture recent output (scrollback) to summarize state like build/test progress, and only then continue with the user’s instructions.

Environments & Example Use Cases

  • Sandbox mode (default): Best for orchestration tasks such as starting a dev server, running builds/tests, and checking results later without host dependencies.
  • Host mode (tmux installed on your machine): Best for workflows needing host access like SwiftUI/Xcode builds or services bound to localhost.

Quick Start

Use the skill to start a persistent session and run a long command by telling the assistant: "Create a tmux session named 'deploy' in ~/myapp and run the deployment command, then tell me the latest output."

Frequently Asked Questions about vellum-terminal-sessions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage long-running terminal commands across different sessions?

You can manage long-running terminal commands by creating persistent tmux sessions that keep processes alive in the background. This allows you to detach from the session and reattach later to monitor progress or send new commands.

Can I run tmux sessions on my local host instead of inside the sandbox?

Yes, you can run tmux sessions on your local host using the host_bash mode instead of the default sandbox mode. This is ideal for workflows requiring access to real host tooling or services bound to localhost.

How do I create a named tmux session and check its build output later?

To create a named tmux session, instruct the assistant to start it in a specific directory and run your build command. You can later capture the session's recent scrollback output to summarize the build progress.

What is the best way to orchestrate multi-step development workflows in a sandbox?

The best way to orchestrate multi-step development workflows in a sandbox is by using persistent terminal sessions. You can start a dev server, run tests, and check results iteratively without losing state.

Does sending commands to a tmux pane support iterative process control?

Yes, sending commands to a tmux pane supports deterministic, iterative process control. You can write or send commands to named shell sessions and read the pane capture to verify the state before proceeding.

When should I not use the default sandbox mode for terminal sessions?

You should not use the default sandbox mode when your workflow requires real host tools or services. In cases like SwiftUI or Xcode builds, switch to host mode to interact with local sessions via host_bash.