Feature: Export AI Conversations as Markdown and PDF

[princenayakpara]

Is your feature request related to a problem?

Currently, CNTRL Browser does not provide a way to export AI conversations for documentation, collaboration, or offline reference. Users who want to save important conversations must manually copy and format the content.

Describe the solution you'd like

Introduce an Export Conversation feature that allows users to export chats in multiple formats:

• Markdown (.md)
• PDF (.pdf)

The exported file should preserve:

• Conversation title
• User prompts
• AI responses
• Code blocks with syntax formatting
• Lists, tables, and headings
• Timestamps (if available)

The export option can be placed in the conversation toolbar or under the overflow menu.

Describe alternatives you've considered

Currently, the only workaround is manually copying the conversation into another editor, which is time-consuming and often loses formatting.

Additional context

Benefits

• Makes it easy to archive important conversations.
• Simplifies sharing AI-generated content with teammates.
• Improves documentation workflows.
• Preserves formatting for technical discussions and code snippets.

Possible implementation

• Add an Export action in the chat interface.
• Support Markdown generation first, followed by PDF generation.
• Reuse existing Markdown rendering logic (if available) for consistent formatting.

Acceptance Criteria

• Export current conversation as Markdown.
• Export current conversation as PDF.
• Preserve formatting (headings, code blocks, lists, tables).
• Handle empty conversations gracefully.
• Provide clear feedback when export completes.

I'd be happy to work on this feature if it aligns with the project's roadmap.

[Jairaj-215xp]

Hi! I'd like to work on this issue as part of ECSoC. Could you please assign it to me?

[Atharv094]

Hi! I would love to work on exporting AI conversations as Markdown and PDF while preserving code blocks and list formatting. Could you please assign this issue to me?

Also, is this issue part of the ECSoC program? If it is, could an admin please add the "EcSoc26" label? Thanks!