Browse commands with the interactive menu

pear --menu opens an interactive, terminal-driven menu for the whole CLI: pick a command from a filterable list, fill in its arguments and flags as a real form, confirm, and Pear runs exactly what typing the equivalent command would have run. It's the fastest way to discover what a command needs without leaving your terminal to check the reference.

Launch the menuCopy Anchor Link

pear --menu

Find a commandCopy Anchor Link

The menu opens on a list of every command, grouped by what you are doing with it:

• Ship—touch, stage, seed, and build: create a link, put files on it, share it, in that order.
• Install & inspect—info, changelog, dump, and install: look at a link, or put it on this machine. None of them changes the link.
• Release—provision and the multisig subcommands: promote a build to production under a signing quorum.
• Network—blind-relay, blind-peer, and identity: help other peers connect and stay seeded.
• Platform—sidecar, cores, gc, data, versions, and help: the local sidecar, storage, and versions. This group starts collapsed because you rarely need it to ship an app.

Move to a command and press enter to choose it. Press enter on a group header to collapse or expand the group. The commands keep their full names under a group, so multisig sign is still pear multisig sign.

Each group has a help panel that explains how its commands fit together. Press F1 or ctrl+k on a group to open it, and esc to close it.

To narrow the list, press / and type. The list keeps the header of each group that still has a match, so you can see where a command lives.

• / — start filtering
• enter — choose the highlighted command, or collapse or expand the highlighted group
• F1 or ctrl+k — open the help panel for the group
• esc — close the help panel
• ctrl+c — quit

Fill in the formCopy Anchor Link

Once you pick a command, the menu builds a real form from its arguments and flags—one field per parameter, using the same descriptions and defaults documented on the CLI reference. Fill in what you need, leave the rest at their defaults, and confirm to run the command. The result is identical to typing the equivalent pear <command> --flags yourself—the menu is a different way to assemble the same call, not a different tool.

• tab — move between fields
• ctrl+s — submit and run the command
• ctrl+c — cancel

Forms with more fields than fit on screen also show ↕ scroll.

From Pear 3.3.0 each field also carries a hint covering that argument or flag's constraints, how it interacts with the others, and how it fails—for example that pear stage --dry-run does not guard --truncate, or that --ignore accepts glob patterns while --only matches by path prefix. These hints appear only in the menu; pear help <command> shows the one-line descriptions without them.

When to use itCopy Anchor Link

Use the menu when you're exploring a command's flags—new to Pear, or new to a command you don't use often—and don't want to context-switch to the reference to check a flag's spelling or default. Use flags directly once you know the shape of the command you want, for scripts, CI, or anything else that needs to run non-interactively.

See alsoCopy Anchor Link

• Command Line Interface (CLI) reference—the full command list the menu is built from.
• Scripting with --json—the non-interactive path for automation.
• Troubleshoot common issues—for problems beyond what this guide covers.