Expand description
ThreadPanel — the editor area’s Ask-workspace content (see CONTEXT.md:
Ask workspace, Thread). Owns the conversation Thread,
the docked question composer, and the live RagClient (when the Kimün
server can answer questions).
The panel is a permanent resident of PanelSet, like the note editor:
its conversation survives the user switching the editor area to
another view because the panel itself is never dropped or moved. Losing the
client (server unreachable / no LLM) disables the composer without evicting
the thread — the thread’s answers are already local.
Input runs through the inherent ThreadPanel::handle_input, not the
Component trait method: the panel derives everything it needs (enabled
state, submission) from its own client, so the trait render (and its
default no-op input) is all the generic dyn Component dispatch needs.
Structs§
- Thread
Panel - The Ask workspace’s editor-area content: the conversation
Threadplus the docked question composer. See the module doc for lifetime notes.
Enums§
- Thread
Focus - Which part of the Ask workspace has keyboard focus within the editor area: the question composer, or the turn list above it.