Overview
Manage your debugging sessions with threads that preserve conversation history and context.
Threads are the core unit of work in Sazabi Chat. Every conversation you have with the assistant is saved as a thread that you can return to later, share with teammates, or fork to explore different directions.
What are threads?
A thread is a saved conversation between you and the assistant. Threads preserve:
- Message history: All your questions and the assistant's responses
- Tool calls: Every search, code execution, and action taken during the investigation
- Artifacts: Charts, tables, diagrams, and other visualizations created
- Context: The assistant remembers everything discussed in the thread
Threads make it easy to pause an investigation and return to it later with full context preserved.
Creating threads
You can start a new thread from several places.
From the dashboard
The dashboard is the primary interface for working with the assistant.
- Open the Sazabi dashboard at app.sazabi.com.
- Click New Thread in the sidebar, or press
Cmd/Ctrl + N. - Type your question and press
Enteror click Send.
The assistant begins investigating immediately. You can continue the conversation by sending follow-up messages.
From Slack
If your organization has connected Slack, you can start conversations directly from your workspace.
- Go to any channel where the Sazabi app is installed, or send a direct
message to
@Sazabi. - Mention
@Sazabifollowed by your question. - The assistant responds in the thread.
Slack conversations are synced to the dashboard, so you can continue them there or share them with teammates who are not in the Slack channel.
From the CLI
The Sazabi CLI supports starting conversations from your terminal.
sazabi ask "Why are we seeing elevated error rates?"The CLI shows the assistant's response inline. For longer investigations, you can open the thread in the dashboard with:
sazabi ask "Why are we seeing elevated error rates?" --openContinuing threads
Every conversation is saved as a thread. You can return to any thread at any time to continue the investigation.
Threads appear in the sidebar, organized by most recent activity. Click any thread to reopen it and continue the conversation. Your previous context is preserved, so you do not need to re-explain the problem.
There is no concept of "closing" a thread. You can always return to any thread and continue the conversation, even months later.
Choosing the right project
Conversations are scoped to a project. The project determines which logs, metrics, and data sources the assistant can access.
When you start a conversation, make sure the correct project is selected in the dashboard header. If you ask about data from one project while another is selected, the assistant will not find the relevant logs.
You can switch projects without losing your conversation. The thread history is preserved, but the assistant will search the newly selected project for subsequent queries.
Keyboard shortcuts
The dashboard supports keyboard shortcuts for faster navigation.
| Shortcut | Action |
|---|---|
Cmd/Ctrl + N | Create a new thread |
Cmd/Ctrl + K | Focus the composer in the current thread |
Cmd/Ctrl + Enter | Send the current message |
Cmd/Ctrl + / | Open the keyboard shortcuts panel |
Thread lifecycle
Threads have a simple lifecycle:
| Status | Description |
|---|---|
| Active | Appears in your sidebar, fully accessible |
| Archived | Hidden from sidebar, accessible from settings |
Active threads are sorted by most recent activity. When you send a message or the assistant responds, that thread moves to the top of the list.
Thread organization
Organizing
Keep threads organized with pinning, renaming, and sidebar sections.
Archiving
Archive completed investigations to keep your workspace clean while preserving history.
Visibility
Control who can see your threads with organization-wide and personal visibility settings.
Collaboration
Sharing
Share thread links with teammates so they can see your investigation and findings.
Multiplayer
Multiple team members can participate in the same thread with real-time sync across clients.
Forking
Create branches from existing threads to explore different hypotheses without losing context.