Overview
How might we design conversation tags & labels so people can trust and act on AI output?
When this pattern fits
- Perfect for professionals, researchers, and teams managing multiple projects or topics who need flexible conversation organization.
When to skip or lighten it
- Users with only a handful of chats.
- Workspaces that already organize via projects or channels exclusively.
- Forced tagging before the first message (add friction later).
States
State model coming soon
Key UX elements
Key UX elements coming soon
Anti-patterns to avoid
Tags that cannot be renamed or merged.
AI auto-tags with no user override.
Filters that hide chats with no way to clear filters.
Personal tags leaking across shared workspaces.
How products use it
| Product | Implementation |
|---|---|
| Gmail | Labels for organizing threads. |
| Notion | Tags and databases for AI and doc sessions. |
| Obsidian | Tags across notes and AI-assisted writes. |
| ChatGPT | Projects and organization affordances for chats. |
Implementation
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Conversation Tags & Labels" AI interface design pattern.
Pattern Definition:Frequently asked questions
Should AI suggest conversation tags?
Yes as suggestions the user can accept or edit. Silent auto-filing surprises people.
Tags vs folders?
Tags allow multiple membership; folders imply one place. Many products offer both.
How does this relate to conversation search?
Tags narrow the set; search finds text inside it. They work best together.
What tags are useful by default?
Project, status (active/done), and sensitivity. Let teams add their own taxonomy.