ls-tmux-shared-session-workflow

Execute guarded commands in shared tmux sessions via tmux_ops.

3|2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/CruxExperts/localsetup --skill ls-tmux-shared-session-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-tmux-shared-session-workflow
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-tmux-shared-session-workflow
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-tmux-shared-session-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the risk of unsafe, unscoped command execution in shared tmux sessions by enforcing session boundaries and sudo gatekeeping.

Core Features & Use Cases

  • Session-scoped command execution: commands run only in the selected tmux session with optional sudo probing.
  • Remote-friendly: supports REMOTE_TMUX_HOST to operate across VMs, containers, or remote hosts via SSH.
  • Structured workflow: uses the tmux_ops tool sequence (pick, probe, send, wait) to maintain control and auditable logs during ops.

Quick Start

Pick a tmux session with tmux_ops, attach to it, and begin guarded command execution in the chosen session.

Frequently Asked Questions about ls-tmux-shared-session-workflow

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

FAQPage Schema
How do I safely execute commands in a shared tmux session?

You can safely execute commands in a shared tmux session by using a tool sequence to pick a session, probe for sudo access, send the command, and wait for output, ensuring all operations remain scoped to that session.

Can I run tmux command orchestration on a remote VM or container?

Yes, you can run tmux command orchestration on a remote VM or container by setting the REMOTE_TMUX_HOST variable. This enables the session management workflow to securely connect and operate over SSH.

What is the best way to manage sudo access before sending commands to a tmux session?

The best way to manage sudo access in tmux is through sudo probing, which validates privileges before execution. This gatekeeping step ensures only authorized commands run within the targeted session.

Does this tmux session workflow support local development environments?

Yes, this tmux session workflow supports local development environments alongside remote operations. It applies session-scoped command execution and sudo probing to both local and remote host workflows.

Why should I use session boundaries when running commands in tmux?

Using session boundaries when running commands in tmux prevents unscoped execution that could disrupt other users. It isolates operations to a selected session, maintaining control and generating auditable logs during operations.

What steps are involved in the tmux_ops command execution workflow?

The tmux_ops workflow involves four steps: picking a target tmux session, probing for sudo access, sending the command, and waiting for execution to complete. This sequence maintains control and auditable logs.