{"version":"2.1.285","anchor":"update-refusal-message-names-the-two-directories","canonical_anchor":"update-refusal-message-names-the-two-directories","heading":"\/update refusal now names both directories involved","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/update-refusal-message-names-the-two-directories","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### \/update refusal now names both directories involved\n\nWhen `\/update` refuses because a session came from another project, the message now names that directory and the current one\n\n**What**\n\n`\/update` will not update a session that was started in a different project directory than the one you are in now. The refusal used to say only that the session was resumed from a different directory. It now names the directory the session belongs to and the directory it is running in.\n\nThe message still tells you to restart with `--resume` to continue on the latest version. `--resume` is the command-line option for reopening an earlier session.\n\n**Why**\n\nYou can see straight away which directory the session came from. That makes it easier to go back there and restart it.\n\n- Area: Slash Commands\n- Names: `\/update`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}