{"version":"2.1.257","anchor":"add-dir-now-explains-why-an-already-accessible-directory-wa","canonical_anchor":"add-dir-now-explains-why-an-already-accessible-directory-wa","heading":"\/add-dir now explains why an already-accessible directory wasn't newly loaded","tier":"notice","area":"Working Directories","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/add-dir-now-explains-why-an-already-accessible-directory-wa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### \/add-dir now explains why an already-accessible directory wasn't newly loaded\n\n\/add-dir now explains why an already-accessible directory was not loaded instead of quietly doing nothing.\n\n`\/add-dir` now explains why a directory that's already accessible wasn't (re)loaded, via a new `onAlreadyAccessible` handler, instead of silently no-opping. This covers cases like the path not resolving to a real location, a symlink leading outside the working directory, or skills being disabled for the session (e.g. \"skills, commands, and agents from additional directories are disabled in this session, so nothing was loaded.\").\n\n- Area: Working Directories\n- Names: `\/add-dir`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}