Evidence record / deepseek-harness

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-deepseek-harness-main-adds-explicit-extra-writable-roots-and-rejects-redirected-or-unsupported-grants

Main adds explicit extra writable roots and rejects redirected or unsupported grants. Main allows deployment-configured additionalWritableRoots under Workspace Write, including an explicitly chosen shared Git administration directory for linked worktrees. It does not discover or grant a parent repository automatically. Enforcing hosts reject invalid or redirected grants. Windows ACL subprocess enforcement refuses extra roots as unsupported before creating grants or a child; filesystem tooling can enforce them separately. The grants apply across sessions in that composition. Startup must receive the configuration again after restart, which can happen through saved YAML without manual re-entry.

Channel: main-unreleased. Half: both. Date: 2026-10-18.

Operator consequence: This could eliminate switching an entire agent to Full access just to operate a linked worktree, but no current tag contains it. Watch for a release and backend-specific tests before changing trial instructions. Choose the exact shared metadata directory and account for the composition-wide scope. This is an additional permission primitive, not a demonstrated repair of the older Linux or spawn CVEs.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-deepseek-harness-main-adds-explicit-extra-writable-roots-and-rejects-redirected-or-unsupported-grants

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact