description, kind
| description | kind |
|---|---|
| Native directory-picker surface: the browser half that drives the host OS chooser for workspace-directory flows; for users and maintainers choosing a picking interaction. | package-reference |
@deepseek-ai/dsh-client-ui-directory-picker-native
English | 中文
Summary
This package provides the native directory-picking surface for the Web GUI: when a workspace flow asks for a directory, a renderless browser occupant opens the operating system's own chooser on the machine running the Host and reports the single outcome — a picked path, a cancellation, or a failure. It fills the two directory-flow slots declared by ui-workspace, composing the client side of the native picking interaction in one cordis.yml row. Choose it when the browser runs on the same machine as the Host; in-process and remote-browser deployments need the -browse surface instead.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Mount this plugin alongside ui-workspace and the host backend dsh-host-directory-picker-native; one cordis.yml row then composes the whole native picking interaction. When a workspace add or picker flow opens a directory request, the user sees the operating system's folder dialog; the picked path is adopted by the workspace flow, and cancelling closes the dialog.
When to choose it
Choose this surface when the browser runs on the same machine as the Host, so an OS dialog can open there. Choose the -browse surface when the browser is remote or in-process and no local chooser exists. The two surfaces fill the same slots, so switching is a composition change, not a code change.
Understand the implementation
Implementation internals — click to expand
Both slot registrations install as one transactional effect through nested ctx.slots.inject() calls, because either declaring entry may activate later or replace its declaration. The occupant arms once per rising open edge, so re-renders never launch a second chooser; settlements ride a ref so the answer reaches the owner's latest handlers. An unmount (HMR replacing the occupant) discards the settlement wholesale: the wire carries no per-request abort, so the host-side chooser survives until answered and its answer lands nowhere. The node half is an empty apply that keeps the plugin on the host roster.
Further Exploration
Read these pages when the picking surface is not enough. They move from the browser half to the host backend and the slots it fills.
- dsh-host-directory-picker-native — the OS chooser backend this surface drives.
- ui-workspace — declares the directory-flow slots and owns the picking conversation.
- ui-directory-picker-browse — the in-app browsing alternative for remote and in-process deployments.
- Web client architecture — how browser plugin rows load and register slots.
Model Experience
None, as the directory chooser is browser chrome; nothing here reaches a model request.
KV Cache effect
None; this package neither assembles nor sends a provider request.
Known Limitations and Deferred Work
These limits define when the native chooser fits. They are current package constraints, not a general picker comparison or a task backlog.
- No cancellation of an open chooser — the wire has no per-request abort, so a chooser already on the host display cannot be closed from the browser; a discarded settlement is ignored.
- Local Host carriers only — an OS dialog opens on the machine running the Host, so in-process and remote-browser deployments need the
-browsecomposition instead. Platform failures surface through the owner's retryable folder dialog.
Dev Note
Working context for maintainers — click to expand
None.