From 11f3ef25494bb0a4bc562756dc7e04cae9c27644 Mon Sep 17 00:00:00 2001 From: kapil971390 Date: Thu, 18 Jun 2026 14:56:50 +0530 Subject: [PATCH] :bug: Fix stale MCP token data after create/regenerate (#10280) Fix the root cause in profile.cljs: remove the optimistic conj from access-token-created and instead chain a fetch-access-tokens after the create-access-token API call succeeds. This ensures all callers get a fresh, server-consistent token list automatically. Suggested-by: niwinz Signed-off-by: kapilvus Co-authored-by: kapilvus --- frontend/src/app/main/data/profile.cljs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/frontend/src/app/main/data/profile.cljs b/frontend/src/app/main/data/profile.cljs index f6eabba1f9..e37dc08e45 100644 --- a/frontend/src/app/main/data/profile.cljs +++ b/frontend/src/app/main/data/profile.cljs @@ -495,9 +495,7 @@ (ptk/reify ::access-token-created ptk/UpdateEvent (update [_ state] - (-> state - (assoc :access-token-created access-token) - (update :access-tokens conj access-token))))) + (assoc state :access-token-created access-token)))) (defn create-access-token [params] @@ -510,8 +508,10 @@ (meta params)] (->> (rp/cmd! :create-access-token params) - (rx/map access-token-created) (rx/tap on-success) + (rx/mapcat (fn [token] + (rx/of (access-token-created token) + (fetch-access-tokens)))) (rx/catch on-error)))))) ;; --- EVENT: delete-access-token