fix(project): contain managed paths within project root - #182
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mishamilovidov
added a commit
to mishamilovidov/dotagents
that referenced
this pull request
Sep 9, 2026
Reconcile the marketplace-name migration with Copilot plugin support (getsentry#166) and project-path containment (getsentry#182). The Copilot marketplace generation call site is corrected to match the two-argument pathMarketplace signature after the merge.
This was referenced Sep 9, 2026
3 tasks
This branch was successfully deployed
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.
Project-scoped commands now reject managed and generated paths that lexically escape the project or resolve outside it through an existing symlink. This covers canonical
.agentsstate, legacy skill targets, MCP, hook and subagent output, plugin runtime projections, and managed gitignore files; symlink aliases that stay inside the project continue to work.Previously a repository could commit an outward-pointing
.agents,.codex, or similar harness directory, or use traversal in[symlinks].targets, causing--project installto persist repository-controlled agent configuration outside the checkout. Install did not execute that configuration, but a later harness session could load the MCP, hook, subagent, or plugin configuration.The containment check resolves the nearest existing ancestor so not-yet-created output paths remain valid. User-scope paths and Git worktree common-directory hooks are intentionally unchanged.