Open the bot last visited, else the coordinator

`/admin/bots` sent the super admin to the coordinator and everyone else to their latest bot, which lost the thread each time the tab was reopened. The conversation pages now record where the browser is in two HttpOnly cookies (`cobble_last_visited_bot_id`, `..._workspace_id`, a year, `Secure` only over HTTPS), and the landing page opens that conversation again, in its workspace when it was one. A stale cookie can't loop: `grabReachableConversation` re-checks it with `grabUserConversation`, the gate the conversation pages use, so a revoked grant, a deleted bot or an archived workspace falls back to the coordinator (super admin) or the latest bot, first workspace, empty page. Signing out clears both cookies so the next user on that browser doesn't land in the previous one's conversation.
2026-10-22 11:18:19 +01:00
parent a8d8b680ad
commit 16f1e7904a
14 changed files with 402 additions and 10 deletions
@@ -0,0 +1,38 @@
+import { setCookies } from "@/src/utils/cookies";
+import isSecureRequest from "@/src/utils/is-secure-request";
+import lastVisitedBotCookies from "@/src/utils/last-visited-bot-cookies";
+
+type Params = {
+    req: Request;
+    res: Response;
+    bot_id: number | string;
+    /**
+     * Null or undefined: the bot's own chat.
+     */
+    workspace_id?: number | string | null;
+};
+
+/**
+ * The page's response with the last-visited cookies set, so `/admin/bots`
+ * opens this conversation again next time. Called from the conversation
+ * pages' `res_transform`, which is why it takes and returns the response.
+ */
+export default function withLastVisitedBotCookies({
+    req,
+    res,
+    bot_id,
+    workspace_id,
+}: Params): Response {
+    const new_res = res.clone();
+
+    setCookies(
+        new_res,
+        lastVisitedBotCookies({
+            bot_id,
+            workspace_id,
+            secure: isSecureRequest({ req }),
+        }),
+    );
+
+    return new_res;
+}