TwickaS/delorun--packages-client-ui-approval ↗★ 1
@deepseek-ai/dsh-client-ui-approval
Approval composer takeover over the scoped Remote Event waterfall
同名パッケージの別リポジトリ
- deepseek-ai/deepseek-harness--packages-client-ui-approval
- whitelonng/dshcode--packages-client-ui-approval
- See-Sol-Lab/DeepSeekGUI--packages-client-ui-approval
- SuperJJ007/papermachine--packages-client-ui-approval
- d4551/deepseek-harness--packages-client-ui-approval
- cherrchen/deepseek-harness-electron--packages-client-ui-approval
インストール
検証済み bundle がないか、互換性チェックに失敗しています。先にリポジトリの説明を読んでください。 README 全文を読む ↗
ドキュメント
README 全文を読む ↗description: "Browser approval UI that answers Host permission requests through the scoped interaction path." kind: "package-reference"
@deepseek-ai/dsh-client-ui-approval
English | 中文
Summary
Browser approval presentation over the Agent-scoped Remote Event waterfall. The plugin publishes each pending request through ctx.uiSession, takes over the Conversation composer, optionally renders correlated Tool detail, and returns the user's decision to the waiting Host request. Use it when a browser must collect approval for a waiting Host operation.
Table of Contents
Focus the approval detail region to approve with Enter or reject with Escape. The mounted plugin reserves both keys against editable shortcuts. Enter on the focused Reject button retains its native reject action. Input controls and IME candidates keep their own keys. Keyboard and pointer actions share one pending-request lock; a withdrawn or replaced request cannot accept another answer, and an earlier failed answer cannot unlock its replacement.
When offered, Always allow is the highlighted primary button. Otherwise, the current-request allow action is primary. Enter in the detail region always grants the limited scope: once for a tool approval, or the current session for CUA. Persistent access requires explicitly activating Always allow. The shortcut reference uses Allow because the caller supplies that scope.
An action rendered in the conversation.approval.action list may call gateAllow to set one gate that every allow answer of the card passes before it is sent: the Allow button, Enter, and the allow of each action and choice. A gate resolves true to send, or false when the person cancelled, which sends nothing and leaves the card answerable; a rejection fails the answer like a failed send. Reject never passes the gate.
Callers can supply localized warning copy through the shared card's optional warning field, with paragraphs separated by blank lines (\n\n). Hovering or keyboard-focusing the tag opens a formatted nonmodal card; clicking or tapping also opens it. The pointer can cross into the card to read or select its text. Leaving both surfaces closes it after a short grace period unless keyboard focus remains inside. Moving focus outside, clicking outside, and Escape also dismiss it without rejecting the request. Hover does not move focus. Moving focus elsewhere also closes a hover-open card, including when a foreground modal takes focus. Switching away from the window or hiding the browser tab closes it without restoring focus. Foreground modals and input-method composition retain their keyboard handling. CSS anchors position the card above the tag with window-edge fallbacks and internal scrolling when space is limited.
Model Experience
None, as this package presents approval requests in the browser and registers nothing model-facing.
KV Cache effect
None; approval request and response rendering does not alter a model request.
Known Limitations and Deferred Work
- The shared
conversation.approval.cardFactory presents reject, allow and an optional always-allow action, with caller-owned scope, subject metadata and answer callbacks. Tool approvals retain their two outcomes. Application consent can reuse the card without adopting tool-approval policy. Subject metadata enables left-aligned content and wrapping actions; callers that omit it retain inherited alignment and a single action row. Icons and labels identify the subject visually; the caller owns identity verification and saved grants. - A request's
grants(full-accessorworkspace-management) reaches the pending approval and the card. For such a request the card renders the Session-scopedconversation.approval.actionlist between its detail and its buttons; each entry receivesgrants,toolName,callId,allow(), which answers the card through the same one-shot lock as its Allow button,answered, true while the card sends or has sent an answer, andcanAnswer(), false from then on and once the request no longer accepts an answer, which an entry with effects of its own reads before each effect. A request withoutgrants, or a list without entries, leaves the card unchanged. - A request's
escalatesTo(workspace-writeordanger-full-access, set by a shell-command or file-operation sandbox escalation) reaches the pending approval and the card. For such a request the card renders the Session-scopedconversation.approval.choicelist in its decision row after Allow once; each entry receivesescalatesTo,toolName,callId,allow(),answeredandcanAnswer()as an action does, andoffer(shown), with which it reports whether it shows a button. While an entry reports one, Allow once draws as a secondary button so the choice is the primary one. A request withoutescalatesTo, or a list without entries, leaves the card unchanged.
Dev Note
Working context for maintainers — click to expand
None.