Unverified50% confidenceFactExact time
In monorepo scenarios, if the session is started only in a sub-package directory, paths of other sub-packages in the same repository are also treated as outside the working directory.
1
Sources
50%
Confidence
Long-term
Relevance
11/3/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedFragment separates the check layer from the business rules: repository-specific rules live in local files that are sourced in by the shared check script, so updating the check logic never touches these local rules.61% similarUnverifiedAfter selecting a folder as the workspace in Claude Code, the model can read, modify and run all files within that directory, but cannot access or modify paths outside that directory.59% similarUnverifiedBox Mount encapsulates the sync logic as a separate process, so the agent can only access files under the mount directory and cannot obtain Box's access token.58% similarUnverifiedIn a Monorepo, modifying one package does not trigger builds of all related projects; unaffected projects are automatically skipped.57% similarUnverifiedEnvironment files, shell history, and editor swap files can bypass prompt inspection; the same script should be run on these files before syncing and the scope of remote copies should be restricted.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1128849API
curl https://kongchang.com/api/v1/knowledge/claims/1128849MCP
get_claim(id=1128849)