MortenHustedandClaude Opus 5.5 544b2455c9 M8: a path in a root reached through a link is told why it is refused ...

When a path can't be resolved (a link that leads nowhere, `..` below a
missing folder), the reason is given only for paths inside a root.
That check compared the path as typed with the roots resolved, so a
root reached through a link (`/tmp/work` on macOS is
`/private/tmp/work`) called its own dangling links "outside the folders
that may be written: /private/tmp/work", and a link out of a root still
had its reason told. The existing part of the path is now resolved
before the comparison, as the roots were.

This is also why `links_that_lead_out_of_a_root_are_outside` and
`outside_paths_are_refused_alike_whatever_exists_there` failed on
macOS, where the temp folder is under `/var` -> `/private/var`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-18 23:53:03 +02:00

..

src

M8: a path in a root reached through a link is told why it is refused

2026-10-18 23:53:03 +02:00

tests

Merge fix/749

2026-10-17 20:48:35 +07:00

Cargo.toml

Open only web links and local libraries from a document

2026-10-17 13:19:13 -06:00

clippy.toml

M8: confine MCP file access with --automation-read-root/--automation-write-root (#715) (#746)

2026-10-17 19:56:20 +07:00