Repository navigation
Pass --no-foreign-personal-context on every muse exec by default - #3
Merged
Merged
Conversation
This was referenced Sep 30, 2026
Without it Muse loads the user's own ~/.claude skills (143 on the reporting machine) and personal rules into every run the bridge makes, and sends that context to Meta with the prompt. buildExecArgs now adds --no-foreign-personal-context, so review, critique, delegate runs, transfer, the stop-review gate and `check --probe` all get it (they all launch through runHeadlessAgent). MUSE_CC_FOREIGN_CONTEXT=1 omits the flag. Transfer does not rely on foreign context: the native path names Muse's bundled `bundled:resume-claude` skill and the transcript path explicitly, and the condensed fallback inlines the transcript. Documented in the README (how the bridge calls Muse, Environment). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rtravellin
force-pushed
the
fix/no-foreign-context
branch
from
October 3, 2026 07:56
70ca540 to
1a138da
Compare
This was referenced Oct 3, 2026
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
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.
Without
--no-foreign-personal-context, Muse loads the user's own Claude Code skills and personal rules from~/.claudeinto every run the bridge makes (143 skills on the machine where this was found) and sends that context with the prompt. Runs made on Claude Code's behalf get the whole personal setup of the user, which is noise for the task and more data leaving the machine than the run needs.buildExecArgsnow adds--no-foreign-personal-context. Every launch goes throughrunHeadlessAgent, so review, critique, delegate runs, transfer, the stop-time review gate andcheck --probeall get it.MUSE_CC_FOREIGN_CONTEXT=1omits the flag for anyone who wants the old behaviour.Transfer does not depend on foreign context: the native path names Muse's bundled
bundled:resume-claudeskill and the transcript path explicitly, and the condensed fallback inlines the transcript.MUSE_CC_FOREIGN_CONTEXTin the Environment table. CHANGELOG entry under Unreleased.runHeadlessAgentwith and without the env var; every exec path the bridge launches (review, critique, run, transfer, stop gate, probe) carries the flag; withMUSE_CC_FOREIGN_CONTEXT=1review and run do not.Independent of #2; both add a line at the top of the CHANGELOG's Unreleased section, so whichever lands second needs a one-line rebase, which I'll do.
Tests: 111/111 locally on Windows.
🤖 Generated with Claude Code