fix: run Lake operations in target process - #244
Merged
Conversation
ejgallego
force-pushed
the
codex/issue-239-lake-env
branch
from
August 30, 2026 20:21
177a169 to
84b7fa1
Compare
ejgallego
force-pushed
the
codex/issue-239-lake-env
branch
4 times, most recently
from
August 30, 2026 22:15
9b7bc2e to
bc9f047
Compare
ejgallego
changed the title
ejgallego
force-pushed
the
codex/issue-239-lake-env
branch
from
August 30, 2026 22:55
bc9f047 to
ff34086
Compare
ejgallego
force-pushed
the
codex/issue-239-lake-env
branch
from
August 30, 2026 23:52
ff34086 to
ef5515f
Compare
ejgallego
marked this pull request as ready for review
August 31, 2026 00:22
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.
This PR keeps Lake workspace loading and zero-build save trace generation in a target-built process, so MCP servers can safely serve projects whose Lean commit differs from the MCP executable.
The broker exchanges only typed JSON metadata with the bundled target helper while continuing to own the Lean server directly. This preserves the target Lake environment and server arguments, keeps live Lake values from crossing Lean ABIs, and retains atomic save-trace publication. MCP accepts either the complete
beam-cliruntime or an explicit command/plugin pair with a sibling helper; standalone same-build daemons continue to use Lake in-process.