$ the-wire · showcase
Sandbox path entries stop silently dropping bracketed directories
By RepoJournal · Filed · About Anthropic · Composed from the cited sources · methodology
1 person shipped this
Three stacked pull requests in anthropics/sandbox-runtime fix a glob-dialect hole that let deny rules slip when a path component contained `*`, `?`, `[` or `]`.
Read a path entry as the path it spells, where that exists anthropics/sandbox-runtime
Entries under a folder whose name holds `*`, `?`, `[` or `]` were read as patterns alone, so with `/w` writable a `denyWrite` on a file in `/w/[WIP] project` left that file writable. An entry is now also read as the path it spells where the character-bearing part exists, and as its tail pattern beneath an existing directory, while the pattern reading stays.
Let a caller mark a path entry literal: `{ path, literal: true }` anthropics/sandbox-runtime
`denyRead`, `allowRead`, `allowWrite` and `denyWrite` accept `{ "path": "...", "literal": true }` alongside a plain string, meaning a path that is never treated as a pattern whether or not it exists. `FilesystemPathEntry` is exported, and `getFsReadConfig()` and `getFsWriteConfig()` carry marked entries in four `literal...` lists.
Glob walk: an `anchor` option, a directory taken as the name it is anthropics/sandbox-runtime
The glob dialect has no escape, so `/w/[WIP] project/**/.env` read `[WIP]` as a character class and matched nothing. `walkGlobPattern` and `expandGlobPattern` now take an `anchor`, a leading run of the path that is a name on disk, with only the remainder compiled as a pattern.
Merge pull request #621 from anthropics/feat/literal-path-marker anthropics/sandbox-runtime
Merge commit for the `{ path, literal: true }` marker, the second of the stack; it lands before the entry-resolution change so the third PR can express the paths it finds as marked entries.
Merge pull request #622 from anthropics/fix/path-entries-read-as-paths anthropics/sandbox-runtime
Merge commit that carries the path-reading change to the default branch, completing the replacement of #608 after the marker and anchor groundwork.
