Skip to main content
New to Mesh Code? Start with Install Mesh Code and Using Mesh Code. If something isn’t working, find your symptom below.

​
‘no build is published yet for …’

The installer found no build for your OS and CPU in the current release. It lists the builds that do exist. On Windows the message reads ‘no Windows build is published yet’. On 32-bit Windows the installer stops earlier with ‘Mesh Code requires 64-bit Windows.’ Builds are published for macOS on Apple Silicon, Windows x64, and Linux x86_64. Intel Macs, 32-bit Windows, and ARM Linux have no build. Watch GitHub Releases for new platforms, or use the Mesh CLI, which runs anywhere Python does. On an Apple Silicon Mac, a Terminal running under Rosetta reports x86_64, so the installer looks for an Intel build. Run uname -m. If it prints x86_64, clear Open using Rosetta on Terminal (Finder → Applications → Utilities → Terminal → Get Info), reopen Terminal, and run the installer again.

​
Linux: the app won’t start

AppImages need libfuse2. The installer warns when it is missing. On Ubuntu 24.04 and later:
On older Ubuntu and on Debian, install libfuse2. Or start the app without FUSE:
If mesh-code is not found, ~/.local/bin is not on your PATH. Run ~/.local/bin/mesh-code directly or add the directory to your PATH.

​
macOS: “Mesh Code is damaged and can’t be opened”

You opened a .dmg downloaded in a browser or received over AirDrop, Slack, or Messages. macOS quarantines those, and the build is not notarised yet, so the only button offered is Move to Bin. Either reinstall with the installer, which avoids the quarantine:
or check the download, then clear the flag. Compare the output of
with the Mesh-Code-arm64.dmg line in that release’s SHA256SUMS on the Releases page. Only if they match, copy the app to Applications and run:

​
‘checksum mismatch … refusing to install’

The download did not match the release’s published checksum, so nothing was installed. Re-run the installer. If it fails again, download the file from Releases and check it against that release’s SHA256SUMS with shasum -a 256 (macOS), sha256sum (Linux), or Get-FileHash (Windows). If it still does not match, do not install it, and email contact@meshapi.ai.

​
Wrong key or typo

Open the Account panel (or the account menu in the sidebar) and click Replace API key. Paste the correct rsk_... key and click Save key. The key is checked against Mesh API before it is saved, so a bad key fails there. Get a fresh one from app.meshapi.ai → API Keys. The dialog shows the key in use as a hint (…a1b2) and where it came from:
  • environment: MESHAPI_API_KEY (or MESH_API_KEY) is set in the environment Mesh Code was started from, and wins over a saved key. Unset it, then restart Mesh Code.
  • meshapi CLI: the key was picked up from the Mesh CLI. Saving a key here replaces it for Mesh Code only; the CLI keeps its own.
  • this app: a key you saved in Mesh Code.
Sign out removes only the key Mesh Code saved. If the Mesh CLI is signed in, Mesh Code falls back to the CLI’s key.

​
Requests fail with 402

Your account balance is at zero, or the key hit its spend cap.
  • Top up at app.meshapi.ai, or raise the key’s spend cap under API Keys (an org or team cap needs your org admin).
  • A cheaper model does not help: every paid model needs a balance above zero. Only models marked free still run. Find them with Free only in the model browser.
This is the same 402 spend_limit_exceeded you’d see from the API. See Mesh API debugging. The totals in the Account panel are this app’s own tally, not your balance; check the dashboard for that.

​
An approval vanished, or a turn stopped early

  • An approval timed out. An approval left unanswered for 15 minutes counts as a rejection, so that step does not run. Answer it before then.
  • ‘stopped after N hops’. The turn hit Max steps per turn. Open Settings (⌘ + ,) and set it to 0 (unlimited), or raise it.

​
It keeps asking, even in Auto or Bypass

The safety checks run in every mode. File reads and writes under sensitive paths such as ~/.ssh, and commands that match dangerous patterns such as rm -r or sudo, come back as a question with the reason stated, even in Bypass. Writes outside the project ask in Accept edits and Auto. In Auto, reading a file and starting a dev server also ask. The checks are a heuristic on the file path and the command text, not a sandbox. See Safety checks.

​
vim, top, or other full-screen programs hang in the Shell panel

The Shell panel is a pipe, not a terminal (PTY), so programs that take over the screen do not run there. Use your own terminal for them.

​
The model browser is empty

The catalog has not loaded. Check that your key is valid (see above) and that https://api.meshapi.ai is reachable from your network, then use Settings › Model → Refresh.

​
Upgrading

Re-run the install command for your OS. It installs the current release over the existing app. See Install Mesh Code.

​
Still stuck?

Email contact@meshapi.ai with your OS, what you did, and what you saw. Send feedback in the sidebar also opens a short form. More options on the Support page.