From bf0828e469027c2d2e12ecabfa4ed2e54f7be72a Mon Sep 17 00:00:00 2001 From: Yichen Jiang Date: Tue, 4 Aug 2026 13:25:26 +0800 Subject: [PATCH] docs(cli): correct the core-web overlay's ui-question rationale The comment claimed `ui-question`'s host half owns the `ask_user_question` registration. That was true and is the exact mechanism that leaked the tool past every preset; with the node half emptied, disabling the row is a UI decision rather than a capability one. --- apps/cli/config/core-web.cordis.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/apps/cli/config/core-web.cordis.yml b/apps/cli/config/core-web.cordis.yml index 6b31c8f424..3535535855 100644 --- a/apps/cli/config/core-web.cordis.yml +++ b/apps/cli/config/core-web.cordis.yml @@ -54,8 +54,11 @@ - id: tool-str-replace-editor disabled: true -# The matching browser controls must not offer host tools that this profile -# omits. ui-question's host half owns the ask_user_question registration. +# The matching browser controls must not offer surfaces whose tool this +# overlay omits: the panels would render for a capability the model does not +# have. Turning the row off no longer removes a tool — `ui-question`'s host +# half is empty and `tool-ask-user` is composed per preset — so this is a UI +# decision now, not a capability one. - id: ui-plan disabled: true