After clicking Execute Command the Quick Command panel only prints "Command sent successfully! … Check the Executions tab to see the results". The actual stdout/stderr arrives seconds later over WebSocket, but the panel never updates. For the primary use-case of the app (run df -h on a box and read the answer) this is two extra clicks and a hunt through a list that may be dominated by automated runs.
Where
public/index.htmlexecuteQuickCommand() – renders a static confirmation.
connectWebSocket() – on command_result it only refreshes the list/modal, never the Quick Command result area.
Suggested fix
Track the returned execution_id(s) and, on the matching command_result broadcast, render stdout/stderr, duration and a success/failure badge directly under the form (per worker in multi mode).
Offer a "View full execution" link that opens the detail modal.
Show a live "running… 3s" indicator until the result arrives.
## Overview
After clicking **Execute Command** the Quick Command panel only prints "Command sent successfully! … Check the Executions tab to see the results". The actual stdout/stderr arrives seconds later over WebSocket, but the panel never updates. For the primary use-case of the app (run `df -h` on a box and read the answer) this is two extra clicks and a hunt through a list that may be dominated by automated runs.
## Where
- `public/index.html` `executeQuickCommand()` – renders a static confirmation.
- `connectWebSocket()` – on `command_result` it only refreshes the list/modal, never the Quick Command result area.
## Suggested fix
- Track the returned `execution_id`(s) and, on the matching `command_result` broadcast, render stdout/stderr, duration and a success/failure badge directly under the form (per worker in multi mode).
- Offer a "View full execution" link that opens the detail modal.
- Show a live "running… 3s" indicator until the result arrives.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
After clicking Execute Command the Quick Command panel only prints "Command sent successfully! … Check the Executions tab to see the results". The actual stdout/stderr arrives seconds later over WebSocket, but the panel never updates. For the primary use-case of the app (run
df -hon a box and read the answer) this is two extra clicks and a hunt through a list that may be dominated by automated runs.Where
public/index.htmlexecuteQuickCommand()– renders a static confirmation.connectWebSocket()– oncommand_resultit only refreshes the list/modal, never the Quick Command result area.Suggested fix
execution_id(s) and, on the matchingcommand_resultbroadcast, render stdout/stderr, duration and a success/failure badge directly under the form (per worker in multi mode).