Terminals: broadcast input to several selected terminals
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- electron, javascript
Research direction
Start by tracing the existing multi-selection handling and the Prompter delivery path; the issue does not name files or tests. Then locate the terminal state model and e2e setup for fake agents. Done means selected terminals receive the submitted text, others do not, unavailable terminals are reported, and the e2e test confirms scrollback does not enter node.data.
Written by the indexing model from the issue text.
Description
Context
Running the same prompt or command in several agents (for example three reviewers, or a fleet of shells during a deploy) means pasting it into each terminal in turn. The canvas already supports multi-selection.
Proposed behavior
- With two or more terminals selected, a "Broadcast" action (toolbar button, palette command, optional shortcut) opens a small composer; submitting sends the text to every selected terminal, using the same delivery path as the Prompter so submission timing behaves per agent.
- Visual cue on each target while broadcasting; a clear "sent to N terminals" confirmation.
- Terminals that are minimized, suspended or on another floor are reported, not silently skipped.
Acceptance criteria
- e2e test with fake agents: text arrives in all selected terminals and none of the others.
- Undo/save state is not polluted (no scrollback in
node.data).
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adaumsilva/OrchestrAI
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
adaumsilva/OrchestrAI#51 ·
-
documentation good first issue help wanted project
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
adaumsilva/OrchestrAI#47 ·
-
documentation good first issue help wanted project
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
adaumsilva/OrchestrAI#46 ·
-
area:ux enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
adaumsilva/OrchestrAI#45 ·
-
area:ux enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
adaumsilva/OrchestrAI#44 ·
All issues in adaumsilva/OrchestrAI
Similar issues
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
DepressionCenter/agentprise#50 ·
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ccomkhj/product-demo#10 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 73/100
-
`at-root-no-redundant` suggested fix breaks `@at-root { ... }` (at-root not followed by a selector)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
stylelint-scss/stylelint-scss#1368 ·