Summary
Bookmarks allow users to mark specific moments within an exploration conversation for easy return. They are a lightweight "save for later" mechanism that sits at the user level (not workspace or team level).
Core Behaviour
- A bookmark captures a specific point in an exploration (a message or response)
- Clicking a bookmark drops the user back into that exact point in the exploration
- Bookmarks persist across sessions
UI Placement
Bookmark Action (In Conversation)
- Appears as a call-to-action alongside each agent response
- Sits next to the "Save to Workspace" action
- Should be a simple toggle (bookmark/unbookmark)
Bookmarks Section (Main Navigation)
- Visible in the main nav bar of the application
- Shows an indicator/badge with the number of active bookmarks
- Clicking opens a list/panel of all bookmarks
- Each bookmark entry shows enough context to identify it (exploration title, snippet of the response, timestamp)
- Clicking a bookmark navigates to that point in the exploration
Scope
- User-level — bookmarks belong to the individual user, not shared
- Cross-exploration — bookmarks can span multiple explorations
- No limit on number of bookmarks (though UI should handle large lists)
Open Questions
- Should bookmarks have labels/tags for organisation?
- Should there be bookmark folders or categories?
- Do bookmarks have an expiry or archival mechanism?
- When navigating to a bookmarked point, does the exploration resume from there, or is it read-only?
- Should bookmarks be searchable?
- Could bookmarks feed into artefact creation? (e.g. "create artefact from these 5 bookmarks")
- What is the relationship between a bookmark and a snippet? Can a bookmarked message also be a snippet? Are they independent concepts?
Future Considerations
This feature needs more detailed design work. The initial implementation should be simple (toggle + list), with room to grow into a more sophisticated reference system.