Read & work with responses

Responses are working material, not just text. Every message carries actions, some carry visible reasoning, and long conversations get their own navigation.

Message actions

Hover any message (or open its menu) to reveal its actions. The set adapts to the message: user messages can be edited and resent, assistant messages can be regenerated or continued, and everything can be copied, shared, or removed.

Reasoning blocks

Reasoning models show their thinking in a collapsible block above the answer. It is collapsed by default — expand it when you want to check how the model got there, and ignore it when you just want the result. The visible final answer stays separate from reasoning, status and error messages, and tool activity, so the response remains clear even while a conversation is still working.

Images, video and audio

Answers carry media, not just text. An image, a video, or an audio clip in a response — one a tool returned, one the model found in the knowledge base, or one you linked yourself — renders inline where it appears in the answer. Video and audio get normal playback controls; images render at the width of the message.

Media has to be served over https. A plain http address, or a clip pasted inline as a data: URL, is removed before the answer is displayed and leaves nothing where the player would be — re-host it, or link the https address instead. Images are the one exception: they may also be inline data: images.

Every response is sanitized before it reaches the screen, so scripts, click handlers, and javascript: links in model output or fetched page content never run. The same filter is what drops unsupported media sources, so when something you expected to see is missing, look at where it is hosted before you blame the answer.

Links and callouts in answers

A link in an answer behaves like the address it carries. A web address opens the page, and a path inside Wingman moves you there. Anything else, a local file path, a bare file name, or an address using a scheme the app does not open, is shown as plain text you can select and copy: it will not open, and it will never take you out of the conversation you are reading.

Callouts written as > [!NOTE], > [!TIP], > [!IMPORTANT], > [!WARNING] or > [!CAUTION] render as highlighted notes rather than plain quotes, so the important line in a long answer stays visible.

Branch a conversation

Branching deserves a habit: when an answer sparks a tangent, branch it instead of derailing the main conversation. The branch opens as a side thread in the right panel with the message as its starting context, and the original topic keeps its flow. Threads are listed with their parent topic in the all-topics drawer.

Follow-ups and the minimap

After many answers, Wingman suggests follow-up questions as chips under the last message — click one to keep momentum. For long conversations, the minimap on the conversation edge shows the message sequence at a glance; click anywhere on it to jump.

The conversation header

The desktop conversation header rounds out the surface: topic tags for labeling work, the notebook toggle for this topic's notes, a share action for the whole topic, a full-width switch, feedback, and the overflow menu with the remaining topic actions.

Message states