Add documentation about colored dots
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- shell
- Domain
- cli, documentation
Research direction
Start by locating the CLI documentation that describes command output and compare it with the colored-dot behavior in the CLI. Document what each dot color, including purple, green, and blue, indicates, then verify that the documentation search can find the new explanation.
Written by the indexing model from the issue text.
Description
Describe the feature or problem you'd like to solve
The meaning of the colored dots in the left column (purple, green, blue, etc) is not explained
Proposed solution
The CLI prefaces output with a colored dot. Purple appears to indicate user-facing output, green for tasks, etc. but the actual meaning is not explained anywhere.
Asking the CLI "what do the different colored dots in the left column of Copilot CLI indicate" does a doc search but returns no answers.
Add this information to the CLI docs.
Example prompts or workflows
No response
Additional context
No response
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
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.
More from github/copilot-cli
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4729 ·
-
area:sessions
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4712 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/copilot-cli#4638 ·
-
Expose large_output_file_path on TaskShellProgress so clients can read complete shell-task output Openarea:tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/copilot-cli#4630 · 1 comment ·
All issues in github/copilot-cli
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·