{"version":"2.1.310","anchor":"plugin-mcp-bash-parsing-and-path-registration-tweaks","canonical_anchor":"plugin-mcp-bash-parsing-and-path-registration-tweaks","heading":"register_repo_root now rejects symlinks that climb out of their folder","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/plugin-mcp-bash-parsing-and-path-registration-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### register_repo_root now rejects symlinks that climb out of their folder\n\nregister_repo_root now refuses paths through a symlink whose target climbs out with extra ..; the Bash parser gains a backslash option\n\n**What**\n\nTwo safety changes:\n\n- `register_repo_root`, the tool that adds a working directory to a session, now refuses a path that passes through a symlink whose target uses \"..\" to climb further up beyond its leading \"..\/\" parts. A symlink is a file that points to another location, and \"..\" means the folder above. The refusal has its own reason, `link_text_climbs`.\n\n- The parser Claude Code uses to read Bash commands (shell commands) now accepts an option for keeping backslashes inside quotes.\n\n**Why**\n\nBoth tighten security. The first stops a symlink from quietly pointing a registered folder somewhere outside where it appears to be. The second affects how quoted backslashes are read when Claude Code examines a command.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}