# Scoped stage artifact access ## What this item changed The server now derives one exact artifact capability for an OpenCode or Pi model-stage visit: its own directory is writable when the edit tool is present, and its own plus completed earlier visit directories in the same run are readable when a file-reading tool is present. No artifact root, sibling, future visit, other run, traversal path, or symlink escape is granted. The scope is empty if the runner cannot validate its artifact root. Pi retains its lease and explicit extension policy; unrestricted shell remains outside this file-tool boundary and is not an OS sandbox. ## Shared documents this change makes stale - `docs/stage-artifacts.md` and `internal/author/skill/references/operations.md` should explain that model-stage artifact directories are usable by the supported file tools only within the exact same-run visit scope, not as a general external-directory permission.