# send_keys_batch

Source: https://libtmux.org/en/dotnet/latest/mcp/tools/send_keys_batch/

> Send input to a pane's program; a shell that receives it runs it with your user's permissions. Send several keystrokes to one pane in order, in a single call. Use for a short interactive sequence — open a file, move, type, save — instead of one call per key. Each operation refuses the named pane in a human-owned mode and, when source input expands, every synchronized input cohort peer. A batch has at most 64 steps and 64 KiB of UTF-8 text. Each delay is 0-2000 ms and all delays together must fit the server wait ceiling.

MCP is in development

Server behavior and tool contracts may change. Tool availability depends on the server configuration.

Send input to a pane’s program; a shell that receives it runs it with your user’s permissions. Send several keystrokes to one pane in order, in a single call. Use for a short interactive sequence — open a file, move, type, save — instead of one call per key. Each operation refuses the named pane in a human-owned mode and, when source input expands, every synchronized input cohort peer. A batch has at most 64 steps and 64 KiB of UTF-8 text. Each delay is 0-2000 ms and all delays together must fit the server wait ceiling.

[All .NET tools](../) · [JSON](../send_keys_batch.json) · [Source](https://github.com/libtmux/libtmux-dotnet/blob/320dc64f4b8b7815842471327a5e6b84a1499bf8/src/LibTmux.Mcp/Policy/CapabilityModel.cs#L598)

## Arguments

* `onError` optional · string

  Stop after the first failed operation, or continue serially.

  Default: `"stop"`.

* `operations` required · array

  Between 1 and 64 bounded pane-input operations, executed serially.

## Schemas

The schema defines required fields, nested values, defaults, and validation constraints.