Skip to main content
Glama
PiMPStudios

claude-tmux-bridge

by PiMPStudios

claude_code

Send prompts to an interactive Claude Code session running in a tmux terminal. Automatically starts sessions, preserves conversation history, and supports context clearing via /clear or /compact.

Instructions

Send a prompt to an interactive Claude Code session running in a tmux terminal.

Sessions and Claude Code are started automatically if not already running. The user can attach to the session at any time to watch Claude work: tmux attach -t {session-name}

SESSION NAMING: workFolder /Users/you/my-roblox-game → session: claude-my-roblox-game No workFolder → session: claude-code

BEHAVIOUR: • If the tmux session doesn't exist it is created automatically. • If Claude Code isn't running in the session it is started automatically. • Only one prompt at a time per session — concurrent calls return a busy error. • Conversation history is fully preserved between calls. • Claude Code has access to all configured MCP tools (Roblox Studio, Godot, Blender, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe prompt to send to the Claude Code session.
compactNoSend /compact to the Claude Code session before delivering the prompt. Summarises conversation history via the Claude API, keeping key context while freeing up space. Use when context is growing but continuity still matters. Slower than clearContext (30–60s). If both are set, compact takes precedence.
timeoutNoMax seconds to wait for a response (default: 300).
workFolderNoAbsolute path to the project folder. Determines the tmux session name and sets the working directory when creating a new session. E.g. /Users/foo/my-project → session "claude-my-project".
clearContextNoSend /clear to the Claude Code session before delivering the prompt. Wipes conversation history entirely — use when starting a new major feature, a new work session, or when Claude Code warns about large context. Fast (< 1s).
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It excels: auto-start behavior, busy error on concurrent calls, full conversation history preservation, MCP tool access, and session naming rules are all clearly disclosed. This gives the agent a robust understanding of side effects and constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with clear sections (SESSION NAMING, BEHAVIOUR) and bullet points. Each sentence carries useful information without redundancy. It is appropriately sized for the tool's complexity, front-loading the core purpose, and every line earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers a wide range of context: session naming, auto-start, concurrency, history, and MCP access. However, it does not specify the return value shape (e.g., whether it returns the full Claude response or just a status), which would be valuable given the absence of an output schema. This is a minor gap in an otherwise thorough description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema itself already documents all parameters in detail, including use cases for compact and clearContext. The main description adds only session naming context, which is also present in the workFolder parameter description. The description provides no significant semantic value beyond what the schema offers, matching the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource statement: 'Send a prompt to an interactive Claude Code session running in a tmux terminal.' It clearly identifies the tool's function and scope. Even without siblings to distinguish from, the purpose is unambiguous and detailed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when the tool should be used, including automatic session creation and the concurrency limitation. It doesn't explicitly name alternatives (no sibling tools exist), but parameter descriptions for compact and clearContext offer strong usage guidance for choosing between them, effectively covering the when/when-not aspect.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PiMPStudios/claude-tmux-bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server