Conversations Guide
Create and manage conversational AI interactions using Nebula’s conversation system for context-aware chat experiences. Conversations are not a separate storage type—they are regular memories differentiated by message role. You “toggle” conversation behavior by providing arole
field when using store_memory()
or store_memories()
(and optionally linking turns with parent_id
). Storage, indexing, and retrieval work the same way as normal memories; the primary differentiator is the speaker via the role
parameter (e.g., user
, assistant
).
Understanding Conversations
Conversations in Nebula are persistent chat sessions that maintain context and history. They enable:- Contextual AI Responses: AI remembers previous messages in the conversation
- Document Integration: Reference documents and collections for informed responses
- Multi-turn Interactions: Build complex conversations over multiple exchanges
- History Management: Track and review conversation history
Use conversations when you need to capture the speaker with a
role
and link turns via parent_id
. See the examples under “Conversation messages” in the
Memory Operations guide for how to store conversational memories with store_memory()
/store_memories()
.Creating Conversations
Conversations are created implicitly when you store the first message with a role. Usestore_memory()
or store_memories()
to create and manage conversations.
Sending Messages
Usestore_memory()
or store_memories()
to add messages to existing conversations. Provide the conversation ID as the parent_id
parameter.
Managing Conversation History
Get conversation history:Conversation Management
List conversations:Update Conversation Metadata
The Python SDK does not currently support updating existing conversation metadata or message content. This functionality is planned for future releases.
- Create a new conversation with the updated metadata
- Copy existing messages to the new conversation (if supported by future API)
- Update your application to reference the new conversation ID
Best Practices
- Clear Titles: Use descriptive titles for easy identification
- Metadata Strategy: Use metadata to categorize conversations
- Context Management: Include relevant documents and collections
- Message Limits: Keep conversations at a reasonable size
- Regular Cleanup: Archive or delete old conversations
Next Steps
- Memory Operations - Store and search memories
- Clusters Guide - Organize memories effectively
- API Reference - Complete API reference