{"version":"2.1.221","anchor":"rename-rejects-names-that-resolve-to-nothing","canonical_anchor":"rename-rejects-names-that-resolve-to-nothing","heading":"\/rename rejects names that resolve to nothing","tier":"use","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/rename-rejects-names-that-resolve-to-nothing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### \/rename rejects names that resolve to nothing\n\n\/rename now tells you when a name is empty or can't be generated instead of silently blanking it.\n\n**What**\n\nRenaming a session now resolves the name before applying it and reports a failure instead of silently setting an empty one.\n\n**Details**\n\n- One message covers a generated name when there is no conversation context to generate from.\n- A separate message covers a user-supplied name that becomes empty once invisible characters are stripped, and repeats the usage line.\n\n**Evidence**\n\n`That name is empty once invisible characters are removed. Usage: \/rename <name>`\n\n**Usage**\n\n`\/rename my-session`\n\n- Area: Slash Commands\n- Names: `\/rename`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}