Skip to main content
Glama

Kill tmux Window

tmux_kill_window
DestructiveIdempotent

Terminate a specific tmux window and its running processes by specifying the session name and window identifier.

Instructions

Kill (close) a window in a tmux session.

Args:

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

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

WARNING: This will terminate all processes running in the window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYesName of the session
windowYesWindow index or name

Implementation Reference

  • The core handler function for the tmux_kill_window tool. It constructs the tmux target from session and window identifiers, executes the 'tmux kill-window' command using the runTmux helper, and returns success/error responses.
    async ({ session, window }) => {
      try {
        const target = formatTarget(session, window);
        await runTmux(`kill-window -t "${target}"`);
    
        return {
          content: [{ type: "text", text: `Window '${window}' in session '${session}' killed successfully.` }],
          structuredContent: { success: true, session, window },
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error instanceof Error ? error.message : String(error) }],
          isError: true,
        };
      }
    }
  • Zod input schema defining parameters: session (string) and window (string or number).
    inputSchema: z
      .object({
        session: z.string().min(1).describe("Name of the session"),
        window: z.union([z.string(), z.number()]).describe("Window index or name"),
      })
      .strict(),
  • src/index.ts:362-402 (registration)
    Full registration of the tmux_kill_window tool with McpServer, including name, metadata, schema, annotations, and handler reference.
    server.registerTool(
      "tmux_kill_window",
      {
        title: "Kill tmux Window",
        description: `Kill (close) a window in a tmux session.
    
    Args:
      - session (string, required): Name of the session
      - window (string or number, required): Window index or name
    
    WARNING: This will terminate all processes running in the window.`,
        inputSchema: z
          .object({
            session: z.string().min(1).describe("Name of the session"),
            window: z.union([z.string(), z.number()]).describe("Window index or name"),
          })
          .strict(),
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
          openWorldHint: false,
        },
      },
      async ({ session, window }) => {
        try {
          const target = formatTarget(session, window);
          await runTmux(`kill-window -t "${target}"`);
    
          return {
            content: [{ type: "text", text: `Window '${window}' in session '${session}' killed successfully.` }],
            structuredContent: { success: true, session, window },
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: error instanceof Error ? error.message : String(error) }],
            isError: true,
          };
        }
      }
    );
  • Helper function used by the handler to format 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 helper utility to execute tmux commands asynchronously, with custom error messages for common tmux failures.
    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;
      }
Behavior4/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true, but the description adds critical behavioral context beyond this: it warns that killing the window terminates all running processes, which is valuable operational insight not covered by annotations. No contradiction with annotations.

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, followed by parameter details and a critical warning. Every sentence earns its place: the first defines the action, the Args section clarifies inputs, and the WARNING highlights important behavioral consequences. No wasted words.

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?

For a destructive tool with no output schema, the description is reasonably complete: it explains what the tool does, documents parameters (via schema), and warns about process termination. However, it lacks details on error conditions or return values, which would be helpful given the destructive nature.

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%, with both parameters clearly documented in the schema. The description repeats the same parameter information in the 'Args' section, adding no new semantic meaning beyond what the schema provides, meeting 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 ('Kill (close)') and resource ('a window in a tmux session'), distinguishing it from sibling tools like tmux_kill_session (for sessions) and tmux_kill_pane (for panes). The verb 'kill' is precise and matches the tool name, avoiding tautology.

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 implies usage context by specifying it targets windows in tmux sessions, but does not explicitly state when to use this tool versus alternatives like tmux_kill_session or tmux_kill_pane. The WARNING provides guidance on consequences, but no explicit comparison to siblings.

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