Conversation and details serve different readers
Conversation view emphasizes the exchange between the person and Claude. It groups adjacent assistant records into coherent turns and keeps tool calls compact so the reasoning is not buried under payloads.
Details view is intended for technical review. It retains richer tool information and makes it easier to inspect what a command, file operation, or agent actually received and returned.
Formatting follows the content
Text is rendered with common Markdown structures such as headings, lists, links, tables, inline code, and fenced code blocks. User images and tool-result images appear beside the turn where they occurred.
Local command output, interrupted requests, slash-command wrappers, and interactive questions receive dedicated presentation rather than being shown as undifferentiated JSON.
Readable does not mean edited by InstaShare
The viewer reorganizes and formats the uploaded records; it does not use another model to summarize or rewrite the conversation. Except for local secret redaction performed by the skill and server-side image rewriting, the substance comes from the source session.