beet

A glanceable, always-running developer dashboard for GitHub. macOS menu-bar app built on Tauri 2 + Next.js. See SPECS.md for the full product spec and ISSUES.md for the V1 build plan.

Landing page: beet.sh (source in docs/, published by GitHub Pages from main).

Install

1. Download the latest .dmg from GitHub Releases (Apple Silicon).

2. Open the .dmg and drag Beet into Applications.

3. Clear the macOS quarantine attribute, then launch Beet:

   xattr -dr com.apple.quarantine /Applications/Beet.app
   

Beet isn't signed or notarized with an Apple Developer ID yet. macOS tags everything downloaded through a browser with the com.apple.quarantine attribute, and Gatekeeper refuses to open unsigned apps that carry it. Usually you'll see "Beet is damaged and can't be opened. You should move it to the Trash." The app isn't actually damaged. The command above removes the attribute from the app bundle (-r covers everything inside it), and after that macOS opens Beet like any other app. Run it after every update you download from the Releases page, since each new download gets quarantined again.

If macOS says instead that Beet "cannot be verified", you can also go to System Settings → Privacy & Security, scroll to the message about Beet, and click Open Anyway. On macOS 15 Sequoia and later, right-click → Open no longer skips this check.

Commands

npm (frontend + Tauri orchestration)

npm install                # install JS deps
npm run dev                # Next.js dev server only
npm run build              # Next.js static export → out/
npm run lint               # ESLint
npm test                   # Vitest (run once)
npm run tauri dev          # boot Next.js + Tauri shell in dev mode
npm run tauri:mock         # same, in demo mode (fixture data, no PAT/network)
npm run tauri build        # release build → src-tauri/target/release/bundle/macos/Beet.app + .dmg

Demo mode

npm run tauri:mock boots the full app with BEET_MOCK=1: the Rust poller serves bundled fixture data instead of calling GitHub, so no personal access token and no network are needed. Useful for trying out or demoing the UI. Quit any running Beet first — the single-instance guard will otherwise just focus the existing app.

cargo (Rust side, run from repo root)

All cargo commands target the Tauri crate via --manifest-path. CI uses --locked to fail on Cargo.lock drift; locally you can omit it.

# Debug build of the Rust binary (what `tauri dev` consumes).
cargo build --manifest-path src-tauri/Cargo.toml

# Same, with --locked — matches CI. Run before pushing if you touched Cargo.toml.
cargo build --manifest-path src-tauri/Cargo.toml --locked

# Rust lint. CI runs this with -D warnings, so any warning fails the build.
cargo clippy --manifest-path src-tauri/Cargo.toml --locked -- -D warnings

# Force a rebuild of just the Beet crate. Useful when icons or other embedded
# resources change but cargo's incremental detection misses it (the Tauri
# `generate_context!` macro embeds icons referenced from tauri.conf.json).
cargo clean -p beet --manifest-path src-tauri/Cargo.toml

# Regenerate the icon set from design/beet-mark.svg.
npx tauri icon design/beet-mark.svg

After regenerating icons, cargo clean -p beet + a fresh npm run tauri dev is the reliable way to flush the embedded icon. macOS may also cache the Dock icon by bundle ID — killall Dock clears it.

Platform

macOS only in V1 (per SPECS.md §13). Tauri can produce Windows/Linux artifacts as a build by-product, but they are not tested or supported.