@agi321/dsh-temp-chat

LIMITATIONS

Known limitations

- Answers go into the conversation only, not the main context, so **the main agent cannot see them**; paste the key points into a normal prompt if it should know. - `/multi-turn` only recognizes the topic segment since the most recent `/single-turn`; to start a new topic, just use `/single-turn`. - Every temp Q&A leaves behind a child session log (same as the built-in `subagent` tool); in the subagent list this layer appears as `temp-chat:单轮` / `temp-chat:续问`, or `temp-chat:single-turn` / `temp-chat:follow-up` when the notice language resolves to English. - The subagent uses the current session's model, but its persona and tool composition come from the plugin's own internal preset (`dsh-temp-chat`), not the session preset. That preset appears in the preset management list (the registry doesn't distinguish internal from user presets); don't pick it for regular sessions. - Transcript rendering and the marker node depend on DSH extension points (`conversation.chat.commandview`, `uiConversation.events.register`, `conversation.chat.node`) and may change as DSH evolves; the visible effect then is the fallback panel or DSH's built-in command card — never a blank screen.