Show current command above input box for demo audience
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the feature or problem you'd like to solve
In demos, when watching user using GHCP CLI, when they submit a command it is nonlonger visible so it is hard for the audience to follow, especially for those that use subtitles and are reading while the command is typedand
Proposed solution
UX Improvement Request — Copilot CLI Command Visibility
Summary
The Copilot CLI UI clears the command input after execution, which makes it difficult for observers during demos to see what command was just run. This reduces clarity when presenting workflows or teaching the tool.
Problem
When a command is executed, the UI refreshes and the previous command disappears from view. In demo or training scenarios, the audience cannot see the command that triggered the current output, which causes confusion and interrupts the flow of explanation.
Expected Behavior
The UI should retain a small, unobtrusive line showing the previously executed command directly above the current input prompt. This would allow viewers to understand what is being demonstrated without relying on verbal repetition.
Why This Matters
- The command can be typed too fast to comprehend
- Improves demo clarity
- Helps audiences follow along
- Makes the CLI more intuitive during presentations
- Reduces friction for trainers and advocates
- Accommodates those using subtitles.
Proposed Enhancement
Add a “last command” line above the input prompt that persists until the next command is run. This mirrors common UX patterns in interactive CLI tools and significantly improves usability in live demos.
If you want, I can also generate a shorter version or a more formal version.
Example prompts or workflows
No response
Additional context
No response
Contributor 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.
Research direction
No file or test is named. Start by locating the CLI input and command-execution entry points, then trace where the input is cleared and the output view is refreshed. Done means the most recently executed command remains visible in a small line above the current input until another command runs, without disrupting normal interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100