fix: Trust filesystem permissions for Vercel roots#2910
Conversation
github-actions
bot
added
bug
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: eea081ce87
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a73c6e5176
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Allowing arbitrary absolute manifest roots means Vercel can no longer assume manifest.root already exists before startup runs commands with it as cwd. Bootstrapping the root in _prepare_backend_workspace() avoids start-time failures for fresh writable paths and matches the workspace setup pattern used by the other sandbox providers.
alfozan
force-pushed
the
scotttrinh/vercel-root-permissions
branch
from
a73c6e5 to
f5b5e33
Compare
3 participants
Instead of trying to constraint the agent to only work in the workspace, allow it to fail freely without sudo.