docs: Show Bash and PowerShell install commands on the CLI feature page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 77/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- documentation
Research direction
The issue identifies the CLI feature page and its two installation areas: the hero and the “Install the CLI” section. Start by locating that page and checking how its Bash command is displayed; add clearly labeled Bash and PowerShell commands in both areas and link to the installation documentation. Done when Windows instructions are visible on the page wherever installation is offered.
Written by the indexing model from the issue text.
Description
Entire Trail: #2653
Problem or use case
A Discord user reported that the CLI feature page makes Windows appear unsupported: it shows only the curl/Bash installation command. They had to visit the CLI repository to discover the Windows installation option via Scoop.
The page currently shows the Bash command in both the hero and the “Install the CLI” section, without a Windows/PowerShell equivalent.
Desired behavior
Show clearly labeled installation commands for both platforms wherever installation is offered on the page:
macOS / Linux (Bash)
curl -fsSL https://entire.com/install.sh | bash
Windows (PowerShell 5.1+)
irm https://entire.com/install.ps1 | iex
These commands match the current CLI README.
Proposed solution
- Add platform tabs or adjacent command blocks to both installation areas.
- Make Windows support visible without requiring a visit to GitHub.
- Link to the installation documentation for alternatives such as Scoop.
Alternatives or workarounds
Visit the CLI repository or installation documentation to find Windows instructions. The Discord feedback highlights that users may assume Windows is unsupported before taking that extra step.
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 475
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 206
Getting set up
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 entireio/cli
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
entireio/cli#2416 · 1 comment ·
Maintainers usually reply within 1 day
-
Stale `entire configure --agent` hints in investigate and review error messagesPossibly taken @suhaanthayyil claimed this 55 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Codex last_assistant_message is parsed then discarded on Stop/SubagentStopPossibly taken @Vishal202-rgb claimed this 46 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
entireio/cli#2064 · 1 comment ·
Maintainers usually reply within 1 day
-
Codex input_image base64 silently destroyed by JSONL redactionPossibly taken @suhaanthayyil claimed this 73 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
netrc credential source accepts a password with an embedded CR/LF that every other source rejectsOpenagent-butler-finding bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jordansmall/spindrift#6268 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 7 days
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
kmesh-net/kmesh#1979 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
caddyserver/caddy#8314 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100