{"version":"2.1.275","anchor":"repl-sandbox-now-scopes-filesystem-looking-strings-to-worksp","canonical_anchor":"repl-sandbox-now-scopes-filesystem-looking-strings-to-worksp","heading":"REPL sandbox now scopes filesystem-looking strings to workspace roots instead of scanning code for imports","tier":"notice","area":"REPL","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/repl-sandbox-now-scopes-filesystem-looking-strings-to-worksp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### REPL sandbox now scopes filesystem-looking strings to workspace roots instead of scanning code for imports\n\nREPL sandbox check now matches file paths against workspace roots instead of scanning code for import statements\n\n**What**\n\nA helper function used by the REPL (the interactive code-execution environment) sandbox no longer inspects input as JavaScript looking for `require`\/`import`-style statements to block with a \"sealed vm context\" error. Instead, it treats the input as a file path: it expands `$HOME` or `~` prefixes, normalizes the path, and checks whether it falls under one of the configured workspace roots, returning true or false instead of throwing an error.\n\n**Why**\n\nThis changes the sandbox's filtering from code-pattern detection to path-based scoping, which is a more direct way to decide whether a given path is inside allowed workspace boundaries.\n\n- Area: REPL\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}