From 71afc8155e9f6cedbb2eb5bca2ada47e921657cf Mon Sep 17 00:00:00 2001 From: Brooklyn Nicholson Date: Thu, 27 Aug 2026 23:23:47 -0500 Subject: [PATCH] docs(desktop): record why the Bots-home new-chat refusal is gone MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Deleting the Bots home deleted the dead end that "Select a Bot or group first." was apologizing for: with nothing selected the center is now an ordinary session and + works there. The refusal still stands for the cases that remain — a group room, and a selected row too orphaned to route. --- apps/desktop/src/plugins/hermes-bots/plugin.tsx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/apps/desktop/src/plugins/hermes-bots/plugin.tsx b/apps/desktop/src/plugins/hermes-bots/plugin.tsx index 5c8edd8f48..577d7db2e8 100644 --- a/apps/desktop/src/plugins/hermes-bots/plugin.tsx +++ b/apps/desktop/src/plugins/hermes-bots/plugin.tsx @@ -469,6 +469,14 @@ export default { // is no bot-owned surface to scope, so leave the workspace on // whatever the user was already looking at — the roster-hydration // effect in BotsPane scopes it the moment a real owner exists. + // + // This is where the Bots home used to claim the center and refuse a + // new chat with "Select a Bot or group first." Deleting the home + // deleted the dead end it was apologizing for: with nothing selected + // the center is an ordinary session and `+` works there. The refusal + // itself still stands for the cases that remain — a group room, and + // a selected row too orphaned to route (setBotsWorkspaceOwner's + // blocked target). if (group) { setBotsWorkspaceOwner( groupWorkspaceOwnerKey(group),