One desktop app for all your Grillings.
Barbecue is the human surface of the async grill system. Begin a Grilling from a Brief, let its local AI Drives derive the Questions, and answer them yourself — over GitHub, Linear, or a local SQL file, with no Barbecue server in between. Humans write every Answer.
Works with the Stores you already use
Grill Queue
Questions
Question Thread
Why Barbecue
Reads like a chat client
The Grill Queue is your channel list. A Grilling is one channel, its topic is the Brief, the AI's Questions are the posts, and every Answer lives in its Question's own thread.
Humans write every Answer
AI only derives Questions and summaries. The Grilling's Author funds each Drive and keeps Answer Selection and Drive Again in human hands.
Bring your own Store
One Active Store Connection switches the whole workspace between GitHub, Linear, or a local SQL file — ordinary Store identities, no Barbecue server, no account.
Threads advance in parallel
The first Drive decomposes a Brief into independently progressable Question Threads, each with its own private Harness Conversation.
Attachments that migrate
Files are imported into the durable Grilling itself, never stored as machine-local paths — so they follow SQLite, GitHub, Linear, refresh, and Store moves.
Native shell, wasm heart
Leptos compiled to WebAssembly inside a Tauri v2 shell. One binary with vendored fonts and an embedded UI — no Electron, no CDN.
Download
Get Barbecue
The latest build of everything merged to master, served straight from this site — the page you are reading and the build it hands you ship together.
Unsigned internal build. On first launch, right-click → Open — see the questions below.
Questions
Who can download this?
Anyone who can reach this site. The button hands you the build directly — no GitHub account, no sign-in, nothing to request. It is still a trusted internal app rather than a shrink-wrapped product, so it is unsigned; read the next answer before you launch it.
Why does macOS warn on first launch?
Builds are not signed with a Developer ID or notarized. On first
launch, right-click the app and choose Open, or allow it under
System Settings → Privacy & Security. If macOS still refuses,
clear the quarantine flag: xattr -rd com.apple.quarantine /Applications/Barbecue.app.
Where does my data live?
In whichever Grilling Store you connect — GitHub, Linear, or a local SQLite file. Barbecue uses your ordinary Store identities and has no server of its own, so there is no Barbecue account and nothing to sync.
Which platforms are supported?
The rolling build targets macOS on Apple Silicon. The app is a plain Tauri v2 workspace, so other targets can be added to the release workflow when someone needs them.
How fresh is "latest"?
Every push to master that touches websites/barbecue/
rebuilds the bundle and redeploys this whole site — page, build and
/latest.json in one image — so the button always hands you
the newest merged build, and the manifest beside it always describes
that exact file. The installed app checks the same manifest and offers
you the update.