██╗███████╗ █████╗ ██╗ ██╗ █████╗ ██╗ ██╗ █████╗ ██║╚══███╔╝██╔══██╗██║ ██╔╝██╔══██╗╚██╗ ██╔╝██╔══██╗ ██║ ███╔╝ ███████║█████╔╝ ███████║ ╚████╔╝ ███████║ ██║ ███╔╝ ██╔══██║██╔═██╗ ██╔══██║ ╚██╔╝ ██╔══██║ ██║███████╗██║ ██║██║ ██╗██║ ██║ ██║ ██║ ██║ ╚═╝╚══════╝╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝
Every repo in your code directory, served as a small plate — git status, last pour, languages, house rules — in a TokyoNight bar that lives in your terminal.
Your editor opens one project at a time. izakaya opens the whole bar. Point it at your code directory and every repo lines up along the counter — newest pours first — so a single glance tells you which ones have uncommitted work, which have drifted untouched for months, and which are clean and ready to ship.
Sit down at any plate and the panel fills in: a Starship-shaped git ribbon, the
last few commits, a 12-week activity sparkline, the languages and size on disk,
the stack it's built on, and whether the kitchen has posted its house rules
(CLAUDE.md). It never touches the repos it serves — browsing is
read-only. Press ↵ and the iz() wrapper sets your shell
down right inside the one you picked.
Nothing to pull from a registry — izakaya is a single file with zero dependencies. Clone it, link it, and the bar is open in under a minute.
Grab the public repo. It's a single bin/izakaya.js — no dependencies to pull.
npm link puts izakaya on your PATH. No build step runs.
iz()A tiny shell wrapper so ↵ can drop you into the repo you picked.
# clone and link — izakaya is one file, zero dependencies $ git clone https://github.com/vajramatt/izakaya.git $ cd izakaya && npm link # → izakaya on your PATH # open the bar — your code dir (it asks on first visit), or any path $ izakaya $ izakaya ~/work # the iz() wrapper — press ↵ on a plate and your shell cd's into the repo # ~/.zshrc iz() { izakaya "$@" local seat="$HOME/.cache/izakaya/seat" [[ -f "$seat" ]] && cd -- "$(<"$seat")" && command rm -f -- "$seat" }
Requirements: Node ≥ 22, a nerd font, and a truecolor terminal (Ghostty,
kitty, iTerm2…). The launch keys (o t e c b y) lean on macOS — browsing the
menu works anywhere Node does. Full docs, keys, and the demo recipe live in the
README.