@deepseek-ai/dsh-client-ui-permission-presets

@deepseek-ai/dsh-client-ui-permission-presets

English | 中文

Permission browser surfaces for two different lifetimes. The General-settings row reads the explicitly exposed permission Settings descriptor, derives its options from the host's dynamic defaultPreset enum, and writes one settings.mutate path operation with the descriptor revision. Its observable rides the slot system's hooks compartment, so the renderer owns React hook binding; a push invalidation refetches the descriptor. This value applies only when a later session is created; changing it does not switch the current session. Choosing Full access requires an explicit risk acknowledgement before the row writes it.

The row follows the shared authorization-aware Settings mirror. Every mutation validates the Host-attached principal identity before accepting the redacted namespace response; a principal generation change synchronously clears the permission value, options, writability, revision, and saving state even while the write is pending. A rejected settlement publishes neither the selected value nor an error from the prior principal.

The current-session surface remains a popupSelect DECORATION hung on the host /permission command (ctx.commandUi.decorate). A decoration is not a second command — the host command keeps its slash-menu row, the argued path (/permission switches directly), and the durable lifecycle logging; the decoration replaces only the bare invocation with the picker: one flat preset list with the current value marked active and built-in presets under their locale product names (workspace-write → 工作区内修改 in Chinese, the composer chip's display transform twin) while host-configured presets keep their own names, where a pick submits the /permission command line. Options and the active mark read the session's permissions projection (the same host-computed select the composer chip renders), so both current-session surfaces share one read source and one write path, and the pushed projection frame is the single confirmation both follow. The decoration is available exactly while the projection key is present; a permission-less composition shows neither picker nor Settings row.

The /client exports are the plugin body (apply/inject).

Model Experience

Indirectly, through the permission facts written by its two surfaces: the Settings row causes a future session to start with whole-value knob events (permission/preset, sandbox/mode, approval/policy), while the /permission picker appends the same facts when it switches the current session; those events select the sandbox mode and approval policy later tool calls resolve, and picker interaction adds no prompt content.

KV Cache effect

No direct invalidation; the knob consumers own any request-prefix changes.

Known Limitations and Deferred Work

• The Settings row is Web-only — non-Web clients may still switch the current session through /permission, but do not receive this browser contribution.