Repository navigation
Let safehouse agents use mcporter's vault - #68
Merged
Merged
Conversation
technicalpickles
enabled auto-merge
October 16, 2026 18:45
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.
Summary
safewith EPERM on~/.mcporter, which is where mcporter keeps its OAuth vault, schema caches and locks.common.sbnow grants it read/write.mcporter.jsonandmcporter.jsoncstay write-denied. They name stdio server commands, so a sandboxed agent that could edit them could get code run unsandboxed the next time mcporter runs outside.common.sbcovers picks up the new grant.Test plan
Ran
safehousedirectly with this branch'scommon.sbandrole-work.sb: readingcredentials.jsonand writing a scratch file in~/.mcporterwork, writingmcporter.jsonor creatingmcporter.jsoncfails withOperation not permitted, and~/.claude.jsonis still denied.🤖 Generated with Claude Code