tmux-mcp

Overview Schema Source Related Servers Discussions Admin

Move terminal pane

tmux_move

Move a pane created with tmux_new into another window by splitting it, so you can view both panes at once without switching focus or stopping the running process.

Instructions

Move a pane tmux_new opened into the window of target_pane, splitting it, so the human sees both at once. Their view does not switch to it. Whatever runs in the pane keeps running. Leaving a session or window empty closes it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "tmux_move"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The name given to tmux_new, or the pane id it returned, e.g. "%7".
`target_pane`	No	tmux target such as "0:1.0" (session:window.pane, from tmux_list_panes); empty = the agent session "agent"

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important side effects: the human view does not switch to the moved pane, running processes keep running, and an emptied source session or window is closed. This adds meaningful behavioral context for a non-destructive but non-idempotent mutation.

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 front-loaded with the action and destination, then adds only relevant behavioral details in short sentences. Every sentence contributes useful information without repetition.

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

Completeness5/5

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

Given full schema coverage, annotations, and an output schema, the description covers the essential behavior and side effects an agent needs. It need not explain return values because an output schema exists.

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 description coverage is 100%, so both parameters are already documented in the input schema. The description reinforces that the pane comes from tmux_new and that target_pane is the destination window, but it does not add syntax or format details beyond the schema.

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 states a specific verb and resource: it moves a pane into the window of target_pane by splitting it. It also scopes the action to panes opened by tmux_new, which distinguishes it from siblings like tmux_new, tmux_send, tmux_read, and tmux_kill.

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?

It gives clear context for when to use it: to relocate a pane created by tmux_new so the human sees both panes at once. It does not explicitly compare alternatives or state when not to use it, but the prerequisite and scenario are clear.

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

Deploy Server