Skip to content
Agentmart
Submit a tool

tmux-interactive-processes

Use tmux instead of background bash for long-running, interactive, inspectable, or user-attachable terminal processes.

Skill by adampoit

IndexedMIT★ 2
Write a review

Chalk Labs

Need help deploying tmux-interactive-processes?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/adampoit-tmux-interactive-processes

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use tmux instead of background bash for long-running, interactive, inspectable, or user-attachable terminal processes. Use for development servers, watch-mode tests, REPLs, debuggers, interactive CLIs, log tailing, and commands that may run indefinitely or need later input/inspection.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/tmux-interactive-processes

What's inside

Skill name
tmux-interactive-processes
Description
Use tmux instead of background bash for long-running, interactive, inspectable, or user-attachable terminal processes. Use for development servers, watch-mode tests, REPLs, debuggers, interactive CLIs, log tailing, and commands that may run indefinitely or need later input/inspection.
License
MIT
Instructions
139 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Tmux Interactive Processes

Use tmux when a command needs to keep running, accept later input, show ongoing output, or remain available for human attachment.

Prefer tmux over raw background shell patterns because the process stays visible, inspectable, attachable, and controllable.

## Avoid Background Bash

Do not use these patterns for long-running or interactive work:

```bash
command &
nohup command &
command > log.txt 2>&1 &
disown
tail -f log.txt
```

Use normal shell execution only when the command runs to completion and prints final output.

## Session Names

Use stable, descriptive names:

```bash
agent-<repo-or-project>-<purpose>
```

Examples:

```bash
agent-myapp-dev
agent-myapp-tests
agent-myapp-debug
agent-myapp-repl
```

Check existing sessions before creating a new one:

```bash
tmux list-sessions
```

Reuse a matching session when appropriate.

## Start Commands

Create a detached session from the current working directory:

```bash
tmux new-session -d -s agent-myapp-dev -c "$PWD" 'npm run dev'
```

For commands with tricky quoting, start a shell first:

```bash
tmux new-session -d -s agent-myapp-dev -c "$PWD" bash
tmux send-keys -t agent-myapp-dev 'npm run dev' C-m
```

Inspect the pane after startup before claiming success.

## Inspect Output

Capture recent output:

```bash
tmux capture-pane -pt agent-myapp-dev -S -200
```

Capture more history:

```bash
tmux capture-pane -pt agent-myapp-dev -S -1000
```

Use `capture-pane` to verify readiness, failures, prompts, and current state.

## Send Input

Send text followed by Enter:

```bash
tmux send-keys -t agent-myapp-dev 'help' C-m
```

Send control keys:

```bash
tmux send-keys -t agent-myapp-dev C-c
```

Use `send-keys` for REPLs, debuggers, prompts, and graceful shutdown.

## User Attachment

When useful, report the session name and attach command:

```bash
tmux attach -t agent-myapp-dev
```

## Stop Sessions

Prefer graceful shutdown first:

```bash
tmux send-keys -t agent-myapp-dev C-c
```

Inspect after shutdown:

```bash
tmux capture-pane -pt agent-myapp-dev -S -100
```

Remove the session only when it is no longer needed:

```bash

From adampoit/ai, MIT.

More from adampoit/ai

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
May 5, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from adampoit

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get tmux-interactive-processes running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying tmux-interactive-processes?

CallGet help
Cite this page

tmux-interactive-processes skill. Agent Mart. https://agentmart.dev/skills/adampoit-tmux-interactive-processes (last updated 2026-10-24)