Threads¶

Learn how to manage conversation threads for organized testing and development.

What Are Threads?¶

Threads are separate conversation streams with an assistant. Each thread:

Has its own message history
Maintains conversation context
Can be continued later
Is independent of other threads

Why Use Multiple Threads?¶

Organized Testing¶

Create separate threads for different test scenarios: - "Product Questions Test" - "Edge Cases Test" - "Knowledge Base Test"

Preserve Context¶

Threads maintain context across messages, useful for: - Multi-turn conversations - Follow-up questions - Complex scenarios

Compare Approaches¶

Test different conversation styles in separate threads without mixing contexts.

Creating Threads¶

New Thread Button¶

Select an assistant in the left panel
Click New Thread
Start typing in the new conversation

Automatic Creation¶

A new thread is automatically created when you: - First interact with an assistant - Need a fresh conversation context

Switching Between Threads¶

Select a Thread¶

View threads listed under the assistant
Click on a thread to switch to it
The conversation loads in the right panel

Thread List¶

Threads show: - Thread name/identifier - Preview of last message - Timestamp

Managing Threads¶

Continuing a Thread¶

Simply select the thread and continue typing. The assistant has context from previous messages in that thread.

Thread Context Window¶

Context Limits

Threads maintain context within the assistant's token limits. Very long conversations may lose earlier context.

Thread Organization Tips¶

Naming Convention¶

While threads may be auto-named, you can organize by: - Testing purpose - Date/time - Specific feature being tested

When to Start Fresh¶

Create a new thread when: - Testing a completely different scenario - Previous context might confuse results - You want to compare fresh responses - The conversation has become too long

When to Continue¶

Continue an existing thread when: - Testing follow-up scenarios - Building on previous conversation - Checking context retention - Simulating real user behavior

Example Workflows¶

Testing Product Knowledge¶

Thread 1: Basic Product Questions

You: What products do you offer?
You: Tell me about Product A
You: How much does it cost?

Thread 2: Comparison Questions

You: Compare Product A and Product B
You: Which is better for [use case]?

Thread 3: Edge Cases

You: What about discontinued products?
You: Do you have Product X? (doesn't exist)

Testing Support Scenarios¶

Thread 1: Order Status

You: Where is my order?
You: It's been 5 days
You: I want to cancel

Thread 2: Returns

You: How do I return something?
You: What's your refund policy?

Thread 3: Complaints

You: I received a damaged item
You: This is unacceptable
You: I want to speak to a manager

Troubleshooting¶

Threads not loading¶

Refresh the page
Check internet connection
Try selecting a different assistant and back

Lost thread history¶

Very old threads may be archived
Check your tier's retention limits
History is tied to the assistant - deleted assistants lose threads

Context seems lost¶

Thread context has token limits
Start a new thread for fresh context
Very long conversations naturally lose older context

Best Practices¶

Do¶

Use descriptive mental notes about each thread's purpose
Start fresh threads for unrelated tests
Keep important test results documented elsewhere
Regularly test fresh contexts

Don't¶

Rely on threads for permanent record-keeping
Mix different test purposes in one thread
Expect unlimited history retention
Forget that context has limits