Skip to main content
Glama

Kill tmux Session

tmux_kill_session
DestructiveIdempotent

Terminate a tmux session and all its windows/panes by specifying the session name. This action stops all processes running in the session.

Instructions

Kill (terminate) a tmux session and all its windows/panes.

Args:

  • name (string, required): Name of the session to kill

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the session to kill

Implementation Reference

  • The handler function for the tmux_kill_session tool. It takes a session name, runs the tmux kill-session command using the runTmux helper, and returns success or error responses.
    async ({ name }) => {
      try {
        await runTmux(`kill-session -t "${name}"`);
        return {
          content: [{ type: "text", text: `Session '${name}' killed successfully.` }],
          structuredContent: { success: true, session: name },
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error instanceof Error ? error.message : String(error) }],
          isError: true,
        };
      }
    }
  • Zod input schema defining the required 'name' parameter (string) for the session to be killed.
    inputSchema: z
      .object({
        name: z.string().min(1).describe("Name of the session to kill"),
      })
      .strict(),
  • src/index.ts:213-249 (registration)
    Registration of the tmux_kill_session tool with the MCP server, specifying metadata, schema, annotations, and handler function.
    server.registerTool(
      "tmux_kill_session",
      {
        title: "Kill tmux Session",
        description: `Kill (terminate) a tmux session and all its windows/panes.
    
    Args:
      - name (string, required): Name of the session to kill
    
    WARNING: This will terminate all processes running in the session.`,
        inputSchema: z
          .object({
            name: z.string().min(1).describe("Name of the session to kill"),
          })
          .strict(),
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
          openWorldHint: false,
        },
      },
      async ({ name }) => {
        try {
          await runTmux(`kill-session -t "${name}"`);
          return {
            content: [{ type: "text", text: `Session '${name}' killed successfully.` }],
            structuredContent: { success: true, session: name },
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: error instanceof Error ? error.message : String(error) }],
            isError: true,
          };
        }
      }
    );
  • Shared utility function used by tmux_kill_session (and other tools) to run tmux commands with custom error handling for common issues like missing sessions.
    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 valuable context beyond this: it explicitly warns that 'This will terminate all processes running in the session,' which clarifies the scope of destruction. However, it doesn't mention authentication needs or rate limits.

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 action, followed by parameter details and a warning. Every sentence earns its place by providing essential information without redundancy, making it efficient and well-structured.

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 complexity (destructive operation with one parameter) and rich annotations (destructiveHint, idempotentHint), the description is mostly complete. It lacks output schema details, but the warning adequately covers behavioral aspects. A minor gap is the absence of explicit error handling or success indicators.

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 the parameter 'name' fully documented in the schema. The description repeats the parameter info in the 'Args' section but doesn't add meaningful semantics beyond what the schema provides, such as format examples or constraints.

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 verb ('kill/terminate') and resource ('tmux session and all its windows/panes'), making the action specific. It distinguishes from siblings like tmux_kill_pane and tmux_kill_window by specifying it affects the entire session rather than individual components.

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 for when to use this tool (to terminate a session and all its contents), but it doesn't explicitly mention when not to use it or name alternatives. For example, it doesn't contrast with tmux_kill_pane for partial termination.

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