Skip to main content
Glama

Split tmux Window

tmux_split_window

Split terminal windows into panes to run multiple commands simultaneously. Configure split direction, size, and starting directory for efficient multitasking.

Instructions

Split a window into panes.

Args:

  • session (string, required): Name of the session

  • window (string or number, optional): Window index or name

  • horizontal (boolean, optional): Split horizontally (default: false = vertical split)

  • start_directory (string, optional): Starting directory for the new pane

  • percentage (number, optional): Size of new pane as percentage (1-99)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYesName of the session
windowNoWindow index or name
horizontalNoSplit horizontally (default: vertical)
start_directoryNoStarting directory for the new pane
percentageNoSize of new pane as percentage

Implementation Reference

  • The handler function that implements the core logic of tmux_split_window by constructing and executing the appropriate tmux split-window command using helpers formatTarget and runTmux.
    async ({ session, window, horizontal, start_directory, percentage }) => {
      try {
        const target = formatTarget(session, window);
        let cmd = `split-window -t "${target}"`;
        if (horizontal) {
          cmd += " -h";
        }
        if (start_directory) {
          cmd += ` -c "${start_directory}"`;
        }
        if (percentage) {
          cmd += ` -p ${percentage}`;
        }
        await runTmux(cmd);
    
        return {
          content: [{ type: "text", text: `Window split ${horizontal ? "horizontally" : "vertically"} successfully.` }],
          structuredContent: { success: true, session, window, horizontal },
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error instanceof Error ? error.message : String(error) }],
          isError: true,
        };
      }
    }
  • Zod input schema defining parameters for the tmux_split_window tool: session (required), window (optional), horizontal (default false), start_directory (optional), percentage (1-99 optional).
    inputSchema: z
      .object({
        session: z.string().min(1).describe("Name of the session"),
        window: z.union([z.string(), z.number()]).optional().describe("Window index or name"),
        horizontal: z.boolean().default(false).describe("Split horizontally (default: vertical)"),
        start_directory: z.string().optional().describe("Starting directory for the new pane"),
        percentage: z.number().min(1).max(99).optional().describe("Size of new pane as percentage"),
      })
      .strict(),
  • src/index.ts:472-526 (registration)
    Registration of the tmux_split_window tool with McpServer, including metadata, schema, and handler reference.
    server.registerTool(
      "tmux_split_window",
      {
        title: "Split tmux Window",
        description: `Split a window into panes.
    
    Args:
      - session (string, required): Name of the session
      - window (string or number, optional): Window index or name
      - horizontal (boolean, optional): Split horizontally (default: false = vertical split)
      - start_directory (string, optional): Starting directory for the new pane
      - percentage (number, optional): Size of new pane as percentage (1-99)`,
        inputSchema: z
          .object({
            session: z.string().min(1).describe("Name of the session"),
            window: z.union([z.string(), z.number()]).optional().describe("Window index or name"),
            horizontal: z.boolean().default(false).describe("Split horizontally (default: vertical)"),
            start_directory: z.string().optional().describe("Starting directory for the new pane"),
            percentage: z.number().min(1).max(99).optional().describe("Size of new pane as percentage"),
          })
          .strict(),
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: false,
          openWorldHint: false,
        },
      },
      async ({ session, window, horizontal, start_directory, percentage }) => {
        try {
          const target = formatTarget(session, window);
          let cmd = `split-window -t "${target}"`;
          if (horizontal) {
            cmd += " -h";
          }
          if (start_directory) {
            cmd += ` -c "${start_directory}"`;
          }
          if (percentage) {
            cmd += ` -p ${percentage}`;
          }
          await runTmux(cmd);
    
          return {
            content: [{ type: "text", text: `Window split ${horizontal ? "horizontally" : "vertically"} successfully.` }],
            structuredContent: { success: true, session, window, horizontal },
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: error instanceof Error ? error.message : String(error) }],
            isError: true,
          };
        }
      }
    );
  • Helper function used by the handler to construct the tmux target string (e.g., session:window.pane).
    function formatTarget(session?: string, window?: number | string, pane?: number): string {
      let target = "";
      if (session) {
        target = session;
        if (window !== undefined) {
          target += `:${window}`;
          if (pane !== undefined) {
            target += `.${pane}`;
          }
        }
      }
      return target;
    }
  • Core utility function used by all tmux tools, including tmux_split_window, to execute tmux commands asynchronously with custom error messages.
    async function runTmux(args: string): Promise<string> {
      try {
        const { stdout } = await execAsync(`tmux ${args}`);
        return stdout.trim();
      } catch (error: unknown) {
        if (error instanceof Error && "stderr" in error) {
          const stderr = (error as { stderr: string }).stderr;
          if (stderr.includes("no server running")) {
            throw new Error("tmux server is not running. Start a session first with tmux_create_session.");
          }
          if (stderr.includes("session not found")) {
            throw new Error("Session not found. Use tmux_list_sessions to see available sessions.");
          }
          if (stderr.includes("window not found")) {
            throw new Error("Window not found. Use tmux_list_windows to see available windows.");
          }
          if (stderr.includes("can't find pane")) {
            throw new Error("Pane not found. Use tmux_list_panes to see available panes.");
          }
          throw new Error(`tmux error: ${stderr}`);
        }
        throw error;
      }
    }
Behavior3/5

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

Annotations indicate this is a non-read-only, non-destructive, non-idempotent, non-open-world operation, covering basic safety. The description adds minimal behavioral context beyond this, such as the default vertical split and percentage range, but doesn't detail effects like pane focus changes or error conditions. No contradiction with annotations exists.

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 core purpose in the first sentence, followed by a structured Args section that efficiently lists parameters without redundancy. Every sentence serves a clear purpose, making it easy to scan and understand quickly.

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?

Given the tool's moderate complexity (5 parameters, no output schema) and rich annotations, the description is mostly complete. It covers the action, parameters, and defaults, but could improve by mentioning typical use cases or interaction with sibling tools. The absence of an output schema means return values aren't explained, but this is acceptable as annotations provide safety context.

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%, providing full parameter documentation. The description adds slight value by clarifying the default for 'horizontal' (false = vertical) and the percentage range (1-99), but most semantics are already in the schema. This meets the baseline for high coverage.

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 clearly states the specific action ('Split a window into panes') with the resource ('window'), distinguishing it from siblings like tmux_create_window (creates new window) or tmux_resize_pane (modifies existing pane). It precisely defines the tool's function without ambiguity.

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

Usage Guidelines3/5

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

The description implies usage for splitting windows but provides no explicit guidance on when to use this tool versus alternatives like tmux_create_window for new windows or tmux_resize_pane for adjusting pane sizes. It lacks context about prerequisites or typical scenarios for splitting.

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/audibleblink/tmux-mcp-server'

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