bet gives you a fast way to find the right repo, inspect it, and jump into it
without memorizing paths or digging through a crowded ~/code folder.
As your local workspace grows, simple navigation gets slower. Repos end up spread across work, client, and side-project folders. bet gives you one fast interface for finding what you need and getting into it.
Search and jump by project slug instead of remembering exactly where a repo lives.
Define your roots once, scan them, and treat your machine like a structured workspace.
Use a shell-native workflow that fits how developers already work instead of forcing a new system.
bet is intentionally simple. You point it at the directories where you keep projects, let it build the index, and then use focused commands to search, inspect, and jump.
Run bet update --roots "$HOME/code,$HOME/work" to scan the places
where you keep your projects.
Use commands like bet list, bet search api, and
bet info payments to locate the right project fast.
Add shell integration once, then use bet go <slug> to move into
projects without breaking your flow.
Think of bet as a focused command set for local project navigation. These are the core workflows most users need day to day.
Run this the first time to tell bet where your projects live.
bet update --roots "$HOME/code,$HOME/work"
Use this when you want a quick view of all known projects.
bet list
Use fuzzy search when you know part of the repo name but not the exact slug.
bet search api
Check metadata or print the absolute path when you want to confirm you have the right project.
bet info marketing-site
bet path marketing-site
After enabling shell integration (add eval "$(bet shell)" to your shell rc file), use bet go to change directly into the
project directory.
bet go marketing-site
Launch the selected project with your configured editor or your system default app.
bet edit marketing-site
If you want bet to refresh itself on a schedule, install a cron update interval.
bet update --cron 1h
Developers already have workarounds. The page should acknowledge that and explain why bet is still useful.
cd, find, or fzf.bet is not trying to replace the shell. It gives frequent project navigation a dedicated, repeatable interface so you spend less time improvising path lookup.
The setup is lightweight: define roots, run update, and use the index. The value is in removing daily friction, not adding process.
bet becomes more valuable as project count grows or work spreads across multiple roots. Even tidy systems benefit from faster search, inspect, and jump workflows.
Install the CLI, build your project index, then enable shell integration so
bet go can drop you into a project instantly.
Use your preferred package manager.
pnpm add -g bet-cli
npm install -g bet-cli
yarn global add bet-cli
Point bet at the directories where you keep code. If you want bet to refresh the index automatically, add the optional cron command after the initial setup.
bet update --roots "$HOME/code,$HOME/work"
optional cron for indexing
$bet update --cron 1h
Add the shell snippet to your rc file, reload your shell, and use
bet go to move directly into a project.
echo 'eval "$(bet shell)"' >> ~/.zshrc
source ~/.zshrc
bet go marketing-site