We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent f74d330 commit 417d211Copy full SHA for 417d211
1 file changed
docs/quickstart.md
@@ -50,9 +50,9 @@ Search all my panes for the word "error".
50
51
When you say "run `make test` and show me the output", the agent executes a three-step pattern:
52
53
-1. {ref}`send-keys` — send the command to a tmux pane
54
-2. {ref}`wait-for-text` — wait for the shell prompt to return (command finished)
55
-3. {ref}`capture-pane` — read the terminal output
+1. {tool}`send-keys` — send the command to a tmux pane
+2. {tool}`wait-for-text` — wait for the shell prompt to return (command finished)
+3. {tool}`capture-pane` — read the terminal output
56
57
This **send → wait → capture** sequence is the fundamental workflow. Most agent interactions with tmux follow this pattern or a variation of it.
58
0 commit comments