Feature Request: Export Conversation as JSON

[nayar-900]

What problem does this solve?

Users often need to save, back up, analyze, or migrate conversations between environments. Currently, there is no straightforward way to export a conversation in a structured JSON format that preserves messages, metadata, timestamps, roles, and other relevant information.

This makes it difficult to:

• Archive conversations for future reference
• Integrate conversation data with external tools
• Debug workflows and agent interactions
• Build custom analytics or reporting pipelines
• Transfer conversations across systems
• Proposed Solution

Add an "Export as JSON" option that allows users to download a conversation as a structured JSON file.

The exported file could include:

• Conversation ID
• Message timestamps
• Sender roles (user, assistant, system)
• Message content
• Metadata and attachments (where applicable)

Benefits

• Easier backup and portability
• Improved developer experience
• Better interoperability with third-party tools
• Supports auditing, debugging, and analytics workflows

Additional Context

JSON is a widely supported format and would make conversation data significantly more useful for automation, integrations, and long-term storage.

[anthonyiscoding]

@nayar-900 can you clarify where you want this JSON export added in iii?

[nayar-900]

Hi Anthony, Thanks for checking in. I’d place the JSON export in the *iii console / UI layer*, not inside a worker or config-level API. Concretely, the expected UX would be: - A button in the console (e.g. “Export Session / Export Trace”) - It exports the full execution trace shown in iii console (calls, worker invocations, inputs/outputs, timing, errors) - Output format: structured JSON that mirrors the trace view so it can be replayed or analyzed externally Optional (nice to have later): - CLI flag like iii export --trace <session-id> - Programmatic API for exporting the same data Main goal is to make what we already see in the live trace UI portable and debuggable outside the console. Let me know if you had a different layer in mind.

…

On Thu, 4 Jun 2026 at 20:23, anthony ***@***.***> wrote: *anthonyiscoding* left a comment (iii-hq/iii#1744) <#1744 (comment)> @nayar-900 <https://github.com/nayar-900> can you clarify where you want this JSON export added in iii? — Reply to this email directly, view it on GitHub <#1744?email_source=notifications&email_token=BKX4GMD66WMIUWZ2HJU7FZD46GIA5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGM2TQMRUHE32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4623582497>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKX4GMFRL6M6L65DQBUUP7T46GIA5AVCNFSM6AAAAACZZEKVPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMRTGU4DENBZG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[sergiofilhowz]

Hi @nayar-900, thanks for sharing this request, it's totally valid. We're working on a new console that is just another worker. https://workers.iii.dev/workers/console the console already has an export conversation.

We're working on revamping the traces view to look more intuitive, and exporting trace should be part of this work. Will keep you posted