Why did Launcher update my app but not its CLI?
ArtCraft Launcher showing a newer graphical app does not establish that a CLI installed separately on macOS changed with it. In Launcher issue #629, one user reported FigCraft 0.12.1 in Launcher while their manually installed figcraft-cli at /usr/local/bin remained 0.11.2. The report is one real setup. Check the app, the CLI your client runs and the release asset as three separate things.

The three versions and paths to distinguish
| Component | Where to look | What its value answers |
|---|---|---|
| GUI Craft App | Version in the app or Launcher | Which graphical app is installed. |
| App-specific CLI | Executable path and its --version output | Which command-line program runs from your shell. |
| MCP client command | Saved command and path in your client configuration | Which executable the client starts for that app. |
The third row is a path, not a second update channel. A client can keep pointing at an older file even when a newer CLI exists elsewhere. Conversely, a CLI can be newer than the GUI: a second comment in the same issue reported SoundCraft app 0.7.0 with CLI 0.8.0. These are user reports, not a statement that every app follows the same installation pattern.
What the official issue says
The original issue, opened 19 October 2026, requests that Launcher install and update macOS CLI assets alongside the apps. It explains that the macOS DMG for the example PdfCraft app held the GUI while pdfcraft-cli was a separate release asset. A later FigCraft comment describes the 0.12.1 versus 0.11.2 mismatch and a manual CLI replacement. As reviewed 6 November 2026, the issue is open; the proposal in the issue is not a released Launcher feature.
The reported version mismatch does not prove an MCP failure by itself. It tells you what to inspect before blaming the app, Launcher or your client.
Check without changing the installation
- Write down the GUI app version shown in Launcher and the app itself.
- In Terminal, command -v figcraft-cli identifies the executable found on your shell path for the reported FigCraft example. figcraft-cli --version shows the installed CLI's own version output. For another app, substitute its actual CLI name from that app's official release page. Different apps format --version output differently; record the full response.
- Open your MCP client's saved configuration and read the exact command it starts. A hard-coded path can differ from the result of command -v in Terminal. Do not paste access tokens or private paths into a public issue.
- Compare the app and CLI versions with the matching official FigCraft releases or your app's official release page. Check the asset name and release date before replacing anything.
Keep the existing CLI and client configuration until you know which component is out of date. The Launcher guide covers the graphical app installation route; the MCP guide covers client registration. This article is a version-and-path check, not a binary replacement tutorial.
Common questions
Does “Update All” prove that every manually installed macOS CLI was updated? No. Issue #629 is a request to add closer CLI management. Check the specific CLI file and its version.
What if Terminal shows the new CLI but my MCP client still uses the old one? Compare the client's configured command with command -v and the path of the new asset. The client may be starting a different file.
Should the GUI and CLI version always match? Compare each with the app's official release assets. The issue contains both older-CLI and newer-CLI reports; a version difference is a reason to inspect the setup, not proof of a broken project file.
Sources
- ArtCraft Launcher issue #629, official tracker; opened 19 October 2026, still open when reviewed 6 November 2026.
- FigCraft 0.12.1 GUI / 0.11.2 CLI user report and SoundCraft version difference report, first-hand comments in that issue.
- FigCraft official releases, the source for matching the reported app's release assets.
Related reading
ArtCraft Launcher guide · ArtCraft MCP and Claude Code guide · PhotoCraft update guide