dsh-prompt-enhance

LIMITATIONS

Known limitations

### The command leaves one line in the transcript DSH renders every admitted command as a persistent flow node. `dsh-client-ui-commands` hardcodes the fallback: ```js text ?? (node.outcome.kind === "error" ? t("command.failed") : t("command.done")) ``` So returning empty text still shows a generic "command done" row. Removing it requires a real typert Remote instead of the command channel — a deliberate larger change, not a bug. ### The model route is explicit, not inherited The plugin does not read the session's own `request/header` route. Configured once per profile; change it when you switch models. ### Draft reading depends on a DOM attribute `[data-composer-input]` is the only source. If DSH renames it, the button reads an empty draft and reports "type something first". ### Multi-line drafts are flattened Command lines cannot contain line breaks, so paragraphs are joined with spaces before the model call. The model usually restores structure; occasionally it does not. ### Rewrites are not diffable The draft is replaced outright. Undo restores it, but there is no side-by-side compare. A preview mode would need a confirm step, which trades away the one-click appeal. ---