From 35dcce14ae6f48fff7bca58ba4f8c0d966593701 Mon Sep 17 00:00:00 2001 From: Andrew Blakeslee Moore Date: Sun, 5 Jul 2026 02:36:28 -0700 Subject: [PATCH] Fix AskUserQuestion Rendering Nucleic-Session: A563CF12-F6B3-498A-8640-97DFC24F59EF Co-authored-by: Nucleic --- NucleicRemote/NucleicRemote/Notifications.swift | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/NucleicRemote/NucleicRemote/Notifications.swift b/NucleicRemote/NucleicRemote/Notifications.swift index fa8ef92..c12a4b5 100644 --- a/NucleicRemote/NucleicRemote/Notifications.swift +++ b/NucleicRemote/NucleicRemote/Notifications.swift @@ -62,7 +62,11 @@ final class NotificationRouter: NSObject { content.title = sessionTitle content.body = "\(approval.toolName) wants: \(approval.title)" content.sound = .default - content.categoryIdentifier = approval.risk.isHigh + // AskUserQuestion collects answers, it doesn't gate — a banner Allow would reply with no + // selection (updatedInput: nil) and the CLI reports the question went unanswered. So, like + // a high-risk approval, it uses the action-less category: it must open the app and be + // answered on the picker card. + content.categoryIdentifier = approval.risk.isHigh || approval.toolName == AskUserQuestion.toolName ? Self.approvalCategory : Self.approvalActionableCategory content.userInfo = [ "sessionID": approval.sessionID.rawValue,