v0.7.0

A project per folder

A folder can now have its own project, so the right key is used in each customer's repository without switching. Outside your home directory, llmenu project asks after the choice:

Applies to
> Only in ~/repos/acme and below
  Everywhere
  Remove the project of ~/repos/acme (use the global choice, …)

Choosing again in the same folder replaces its project. Subfolders follow it, a global switch leaves it alone, and LLMENU_PROJECT still wins. Without the picker: llmenu project use acme --here and llmenu project unpin. llmenu project list shows all bound folders. The bindings live in llmenu's config, not in the repository.

A default tool for llmenu

llmenu without a command can now start your tool after the menu, so you need not type llmenu claude every time. The setup asks for it; if you are already set up, llmenu asks once. Change it with llmenu default (a list), llmenu default codex, or llmenu default --none to only print the model name. Captured as in "$(llmenu)", it always prints only the name, so scripts keep working.

llmenu reset

Removes everything llmenu stored, to start over or before uninstalling: settings, all keys in the keyring (projects included), caches, and the provider entry llmenu sync wrote into pi and opencode (the previous file stays as *.bak; entries llmenu did not write stay). It lists what it removes and asks first; --dry-run only lists, --yes skips the question. The README's manual removal steps are replaced by it.

Upgrade

brew update && brew upgrade --cask llmenu