{"version":"2.1.248","anchor":"repo-root-registration-returns-the-requested-path-in-some-mo","canonical_anchor":"repo-root-registration-returns-the-requested-path-in-some-mo","heading":"Repo-root registration returns the requested path in some modes","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/repo-root-registration-returns-the-requested-path-in-some-mo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Repo-root registration returns the requested path in some modes\n\nRegistering a directory can now echo back the path you asked for rather than the resolved one.\n\n**What**\n\nAfter registering a directory, the reply's directory field is the path you asked for in one mode and the resolved path otherwise; it was always the resolved path before.\n\n**Details**\n\n- Failures now go through one handler that receives the tool name, and directory-add path resolution errors are logged in detail before a sanitised failure is returned.\n\n**Evidence**\n\n`register_repo_root: directory is outside the allowed registration scope`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}