LaunchRanked
Launch free

Launch guideDeveloper tools

How to launch a CLI tool

CLI tools live or die on the install line. If someone can copy one command and run your tool, they'll try it. So the launch work is packaging: a Homebrew tap on day one (homebrew-core has notability rules), winget for Windows, and whichever language registry your users already use. Then a terminal recording that shows the tool doing something useful in seconds.

Updated · platform facts checked against the official docs linked below

At a glance

homebrew-core notability
30 forks, 30 watchers or 75 stars (self-submitted: 90/90/225); repo 30+ days old[1]
Day-one Homebrew option
Your own tap[1]
Windows
winget manifest via pull request[2]

Where people find CLI tools

  • Hacker News (Show HN): Terminal tools are a natural fit if the install is one line.
  • Homebrew: Mac and Linux developers expect brew install.
  • GitHub: Topics like cli and your language get the repo onto browse pages.
  • Awesome lists for your language or shell: Curated lists developers search when they need a tool.
  • Language communities: A Rust CLI launches in Rust communities; a Go CLI in Go ones.

Assets to prepare

Assets to prepare before launch
AssetSpec or guidance
Install commandsOne line per platform: brew, winget, npm/pip/cargo, plus a binary download.
Terminal recordingA short GIF or asciinema cast showing a real task.
`--help` outputClear, grouped and copyable; people read it before your docs.
Homebrew tapA homebrew-<name> repo with your formula until you meet core's notability bar.[1]
winget manifestYAML per the Windows Package Manager schema.[2]
Release binariesSigned where possible, with checksums, on GitHub Releases.

Store and listing rules

What the platform itself says, with a link to the page we checked.

  • homebrew-core accepts new packages with at least 30 forks, 30 watchers or 75 stars (90/90/225 if you submit your own), from a repo at least 30 days old. Below that, use a third-party tap.[1]
  • winget submissions are YAML manifests submitted to the public winget-pkgs repository and must follow its policies.[2]
  • Show HN titles start with "Show HN" and the thing must be ready to try.[3]

A 4-week launch timeline

  1. Week 1 · four weeks out

    • Polish --help, errors and exit codes.
    • Set up release builds for macOS, Linux and Windows.
    • Create your Homebrew tap.

  2. Week 2 · three weeks out

    • Record the terminal demo.
    • Write the README: what, GIF, install lines, examples.
    • Write the winget manifest.

  3. Week 3 · two weeks out

    • Beta with ten developers; watch them install on different machines.
    • Fix install failures first.
    • Draft Show HN.

  4. Week 4 · launch week

    • Tag v1.0 with release notes.
    • Submit the winget pull request.
    • Write docs pages for the top three tasks.

Launch-day checklist

  1. Post Show HN with install lines in the first comment.
  2. Post in your language's community.
  3. Answer install issues immediately; they're the most common launch-day blocker.
  4. Add the project to LaunchRanked with a link to docs.

After launch: SEO steps

Launch boards reset; search pages don't. These steps keep people finding you after launch week.

  1. Write pages for "how to {task} from the command line" searches.
  2. Document each command on its own page with examples.
  3. Link docs, repo and package pages to each other.
  4. Once you meet the bar, submit to homebrew-core for the shorter install command.

Common mistakes

  • Only supporting curl | sh installs.
  • Submitting to homebrew-core before meeting the notability bar.
  • A README with no example output.

Templates for this launch

FAQ

Can I get my CLI into Homebrew on launch day?

Into your own tap, yes. homebrew-core requires notability (for example 75 stars, or 225 if you submit your own project) and a repo at least 30 days old.

How do I distribute a CLI on Windows?

Publish release binaries and submit a winget manifest to the community repository; many developers also use language package managers.

What should a CLI launch post show?

A one-line install and a short terminal recording of a real task. That's what gets people to try it.

Where do CLI tools get discovered?

Show HN, GitHub topics, awesome lists and the language community. Search brings people later through docs pages.

Sources

  1. Homebrew: Package acceptance policy
  2. Microsoft Learn: Submit packages to Windows Package Manager
  3. Hacker News: Show HN guidelines

Checked . Platforms change their rules; open the source before you rely on a number.

Related launch guides

← All 35 launch guides