dsh-followup-suggestions

LIMITATIONS

Known limitations

- **Only the last reply of the session you are viewing**: intentional (fewer calls, no noise), not precomputed per session. - **Two DOM/seat contracts**: a Turn record carrying `status`/`turn`, and `useChat().timeline.turnOrder`. If ui-chat changes either, `lib/client.js` needs the matching update. - **Depends on ui-conversation's `inputActions` and composer DOM**: without that seat the chips still render but clicking does nothing; if `data-conversation-content`/`data-conversation-session`/`data-composer-input` are renamed, a click still fills the draft but no longer moves the keyboard. - **Cached chips live 7 days by default**: one Turn's suggestions stay stable that long, and the refresh icon is the way to ask for a new batch. Clearing `dsh.followupSuggestions.v1` from `localStorage` does the same thing by hand. - **A refresh costs one model call**: by design — it is the only action that bypasses both caches. - **The Host cache is process memory**: nothing is written to disk and it empties on restart. - **Host-side code changes need a restart**: loaded modules are cached in the process (entry `config` changes are the exception — those reload immediately, and the refresh button still works because its request misses the old Host's cache key by construction). - **No session pollution**: suggestions live only in browser `localStorage` and Host memory, never in the Session log, so they never appear in an export.