Ghira
Docs menu

Get started

Install from source

Build and run Ghira on a Mac from source

Ghira is pre-release. There is no signed download yet, so you build the Mac app yourself. This page takes you from a clean Mac to a running app.

What you need

Build and run

Terminal
git clone https://github.com/nhtera/Ghira.git && cd Ghira
git submodule update --init                  # not --recursive
pnpm install && pnpm build
./tools/scripts/build-nemo.sh                # speech engines (Metal)
pnpm --filter @ghi/desktop tauri dev --features nemo

Here is what the commands do:

  1. Clone the repository. The speech engine lives in a git submodule. Run git submodule update --init without --recursive: the engine nests large repositories Ghira does not use.
  2. Build the interface. pnpm install && pnpm build builds the web interface the desktop app shows.
  3. Build the speech engines. ./tools/scripts/build-nemo.sh builds NeMo-Speech.cpp with Metal. It takes a while the first time.
  4. Start the app. pnpm --filter @ghi/desktop tauri dev --features nemo builds and opens Ghira.

First launch

Ghira walks you through setup. The step that matters here is Speech models: the app downloads the models for your Mac's preset (about 3.4 GB on Light, about 4 GB on Balanced and Max) from Hugging Face, and checks each file before it uses it. You can keep going while they download. See Speech models for what is downloaded and how to install the files without a network.

Record your first meeting covers the rest of the setup.

Fetch models for development

If you work on the code, you can fetch the same pinned models into ./models without the app:

Terminal
./tools/scripts/fetch-models.sh                  # all the standard models
./tools/scripts/fetch-models.sh nemotron-3.5-asr # or name the ones you want

The model ids are in crates/ghi-models/registry.toml. Models marked optional, such as the Whisper models, are skipped unless you name them.

A development build is not a release build

tauri dev makes a debug build. A debug build keeps the encryption key for your meetings in a file next to the data folder, not in the Keychain. Do not keep real meetings in a debug build. To use the Keychain in a debug build, set GHI_KEYSTORE=keychain before you start it.

To build an app bundle and a disk image for testing, run tools/release/build-dmg.sh --adhoc. The result is signed ad hoc, so macOS treats it as an unknown developer's app.

Troubleshooting

Limits

Edit this page on GitHubLast updated