working with the dev brain gets asked for confirmation because files in the dev brain are seen as "outside the project" but should always also be seen as part of the project, even if they are in a different tree.
working with the dev brain gets asked for confirmation because files in the dev brain are seen as "outside the project" but should always also be seen as part of the project, even if they are in a different tree.
hugo
added the bug label 2026-08-02 12:25:46 +00:00
The shell approval pipeline now treats the enabled, canonical Dev Brain vault as a trusted path root alongside the selected project. Both heuristic and AI-based risk assessment receive that root; quoted paths with spaces use shell-aware parsing and component boundaries prevent similarly prefixed sibling folders from being trusted. Destructive, network, privilege, application-control, credential, and genuinely outside-path risks still require approval. The behavior is documented in docs/USER_GUIDE.md.
DS4 has no Dev Brain or corresponding permission behavior, so this is DS4Server-specific.
Verified with focused heuristic/AI trusted-root tests, cargo fmt --all -- --check, cargo clippy --all-targets --all-features -- -D warnings, make bundle, and cargo test --all-features (169 passed, 13 ignored hardware/browser fixtures).
Implemented in f62a706.
The shell approval pipeline now treats the enabled, canonical Dev Brain vault as a trusted path root alongside the selected project. Both heuristic and AI-based risk assessment receive that root; quoted paths with spaces use shell-aware parsing and component boundaries prevent similarly prefixed sibling folders from being trusted. Destructive, network, privilege, application-control, credential, and genuinely outside-path risks still require approval. The behavior is documented in docs/USER_GUIDE.md.
DS4 has no Dev Brain or corresponding permission behavior, so this is DS4Server-specific.
Verified with focused heuristic/AI trusted-root tests, cargo fmt --all -- --check, cargo clippy --all-targets --all-features -- -D warnings, make bundle, and cargo test --all-features (169 passed, 13 ignored hardware/browser fixtures).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
working with the dev brain gets asked for confirmation because files in the dev brain are seen as "outside the project" but should always also be seen as part of the project, even if they are in a different tree.
Implemented in
f62a706.The shell approval pipeline now treats the enabled, canonical Dev Brain vault as a trusted path root alongside the selected project. Both heuristic and AI-based risk assessment receive that root; quoted paths with spaces use shell-aware parsing and component boundaries prevent similarly prefixed sibling folders from being trusted. Destructive, network, privilege, application-control, credential, and genuinely outside-path risks still require approval. The behavior is documented in docs/USER_GUIDE.md.
DS4 has no Dev Brain or corresponding permission behavior, so this is DS4Server-specific.
Verified with focused heuristic/AI trusted-root tests, cargo fmt --all -- --check, cargo clippy --all-targets --all-features -- -D warnings, make bundle, and cargo test --all-features (169 passed, 13 ignored hardware/browser fixtures).