fix(setup): register MCP sidecars from a stable path off the DMG (v1.0.1)#2
Merged
Merged
Conversation
When Lumen runs directly from the mounted DMG (or a Gatekeeper App Translocation mount), find_binary() resolves the lumen-mcp/lumen-tok sidecars to their location *inside* that ephemeral mount and writes those absolute paths into ~/.claude.json. Once the DMG is ejected the paths vanish, so Claude Code fails to start the server with: ENOENT: no such file or directory, posix_spawn '/Volumes/dmg.XXXXX/Lumen.app/Contents/MacOS/lumen-mcp' Add stable_binary(): when the resolved sidecar lives on an ephemeral mount (/Volumes/... or .../AppTranslocation/...), copy it into ~/Library/Application Support/io.speedata.lumen/bin/ and register that stable path instead. Copying the standalone Mach-O preserves its embedded signature so it still launches. Non-DMG installs are unaffected. Bump to v1.0.1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Launching
Lumen.appdirectly from the mounted DMG (the default user behavior before dragging to /Applications), or any unsigned/quarantined launch that triggers macOS App Translocation, makes setup record a sidecar path that lives inside a transient read-only mount:find_binary()resolveslumen-mcp/lumen-tokas siblings of the running exe and writes those absolute/Volumes/…paths into~/.claude.json. Once the DMG is ejected the paths vanish and Claude Code can no longer spawn the MCP server.Fix
Add
stable_binary(): when the resolved sidecar sits on an ephemeral mount (/Volumes/…or…/AppTranslocation/…), copy it to~/Library/Application Support/io.speedata.lumen/bin/and register that stable path. Copying the standalone Mach-O preserves its embedded code signature, so it still launches. Normal/Applicationsinstalls are unaffected (no copy). Re-running setup repairs an already-broken~/.claude.json.Bumps version to v1.0.1 + CHANGELOG entry.
cargo check -p Lumenpasses.