Feature Request: Mobile Message Branching, Chat Merging & Lightweight Media Archiving

Feature Request: Mobile Message Branching, Chat Merging & Lightweight Media Archiving

I’d love to see more advanced long-chat management features added to the mobile app, especially for power users managing ongoing projects, technical workflows, and media-heavy conversations.

1. Message / Line Selection for New Chat Branching (Mobile)

The web version already supports workflows similar to:

• “Select message → Start a new chat from this”

• “Select message → Ask about this inside the conversation”

Bringing similar functionality to the mobile app would be extremely useful.

Especially in long conversations, this would help users:

• isolate specific technical problems,

• branch prompts into separate workflows,

• continue older ideas independently,

• keep complex chats organized,

• analyze selected messages while preserving context.

On mobile, long-pressing a message or message group could offer options like:

• “Continue as new chat”

• “Branch from this message”

• “Create new chat from selected messages”

• “Ask about selected messages”

This would significantly improve the mobile UX for advanced and long-term usage.

1. Chat Merge / Conversation Grouping System

Currently, conversations become fragmented over time, especially when the same project is spread across multiple chats.

Instead:

• multiple chats could be selected via long-press,

• a “Merge Conversations” option could be added,

• AI could organize merged chats chronologically and contextually under a unified project/thread.

Example use cases:

• collecting scattered conversations related to the same brand or project,

• centralizing technical troubleshooting,

• organizing ongoing health/work/software processes,

• building a persistent long-term project memory.

This would be especially valuable for power users with heavy and continuous usage patterns.

Additionally, after merging, AI-assisted organization features could automatically generate:

• timelines,

• topic sections,

• duplicate cleanup,

• key decision summaries,

• task lists,

• pinned critical notes.

1. Lightweight Digital Asset Archiving System

In long conversations, generated:

• images,

• videos,

• audio files,

• large output packages,

• rendered assets,

• code outputs

can gradually impact chat performance and responsiveness.

Instead, the system could:

• store optimized hash/reference-based records of generated assets,

• display only lightweight previews and metadata inside the conversation,

• unload heavy assets from active chat memory.

If needed, users could later:

• “Reload asset”

• “Restore original quality”

• “Regenerate this output”

• “Use this generation as reference”

This approach could help:

• conversations remain smoother,

• mobile devices use less memory/resources,

• reduce server load,

• archive older projects more efficiently.

For users heavily focused on image/video generation and long-term workflows, this could become a very powerful optimization feature.