Send to multiple terminals

What it's for

Sometimes the same command needs to run in several terminals: a git status in the three projects before you start the day, a git pull in every folder, the same short question to two agents. Typing broadcast sends one line to every marked pane at once. It is tucked away as an advanced feature on purpose, because a mirrored Enter acts on several terminals at the same time. That is why sending asks for confirmation, and PrumoGrid does not type into a pane that is not in a state to receive it.

When to use it and when not to

Use it for short, one-line commands that every destination needs to receive identically: queries such as git status --short, git fetch, npm test. It also works for sending the same quick question to two agents, such as "Which branch are you on?".

Don't use it to:

• Give an agent a task you want to track. Broadcast does not create a stage, does not show up in the Flow and does not wait for the agent to finish. That is what New stage is for.
• Check work. Receiving the text does not prove the work was done; what checks it is each stage's verification.
• Answer permission requests. A pane that is asking for permission is left out of the send, on purpose.
• Send multi-line text. Broadcast sends one line at a time.

Step by step

The example sends git status --short to the PowerShell terminals of the three demo projects.

1. In the selector at the top, choose All projects, so the terminals of loja-api, portal-web and pagamentos are in the Grid at the same time.
2. Open a PowerShell in each project, if there isn't one yet. Each one starts in its project's folder.
3. In the NEW row, above the terminals, click typing broadcast (advanced)…. The send bar appears, with mark at least 2 panes.
4. Mark each PowerShell with the broadcast icon in the pane header, or click the pane and press Ctrl+Shift+B. The bar now says 3 panes marked, and each marked pane shows that it is in the group.
5. Check the names and folders of the marked panes. If you marked one too many, press Ctrl+Shift+B on it again to take it out.
6. In the type and press Enter: goes to every checked terminal field, write git status --short.
7. Press Enter or click Send. The button turns into Confirm in 3, and a notice asks you to confirm sending to 3 panes.
8. Press Enter again, or click Confirm in 3. The line is typed into the three terminals and runs.
9. Read the summary, for example Line sent to 3 panes. If any pane was left out, the summary says which one and why.
10. To finish, click Leave broadcast. The panes leave the group and focus returns to the terminal you were in.

The confirmation applies to the line you saw. If you change the text after arming the send, the next Enter arms it again and asks for another confirmation, without sending anything.

What you see on screen

Enlarge screenshot ↗

Who doesn't receive it, and why

Before typing, PrumoGrid checks the state of each marked pane. These are the reasons that appear in the summary:

• session ended: the terminal no longer has a live process.
• pane waiting for an approval: the agent is showing a permission request. Typing there would answer the request, so the pane is left out. Answer in the terminal or in See request, and resend if it still makes sense.
• the pane is not at the prompt: a command is still running in a regular shell. Wait for it to finish.

CLI agents, such as Claude Code and Codex, receive the line normally while they show their own interface. The Enter goes separately from the text, after a short pause, so both submit the same way.

The summary also goes into the project log, with a line such as "broadcast typed one line into 3 panes" and, when it applies, who was left out.

Sensitive terminal

A pane whose title or folder matches a sensitive pattern asks for confirmation before joining the group. The Sensitive pane dialog asks whether you want to include that pane and reminds you that everything you type also goes to it. Confirm with Include anyway only if that is what you mean. If a pane becomes sensitive after joining the group, for example because it changed folders or was renamed, it leaves the group on its own and needs to be marked again.

The default patterns are prod, produc, prd and hml, looked for in the pane name and folder, ignoring case. A name like API prod is enough. See Terminal name and sensitive pane.

Tips

• Start with commands that only read, such as git status and git log -1. Leave commands that change files for when you already trust the selection.
• To include only some terminals of a project, select the project instead of All projects and mark the panes you want.
• Dragging a file or image onto a terminal inserts the path only in that terminal, even with broadcast on.
• After sending a question to two agents, read each one's answer in Focus. Broadcast does not combine the answers.

Known limitations

• One line per send. Text with a line break is refused with the notice Send one single line at a time.
• It needs at least two marked panes.
• Broadcast does not create a stage, does not record completion and does not verify results.
• Panes waiting for permission, with no session or with a command running in the shell are left out of that send.