Skip to main content
A thread is a conversation with the Sazabi agent about your systems, and it is the unit of every investigation. This page covers how to start one, keep it in sync across surfaces, control who can see it, share it, fork it, search your history, and archive it.

​
Starting a thread

Open your project in the dashboard and type a question in the composer. That starts a thread. You can also start one from Slack or Microsoft Teams, the CLI, the API, or your coding agent — every surface reaches the same threads (see below).

​
Start anywhere, stay in sync

A thread is not tied to the surface you started it on.
  • Surfaces. Threads can originate from the web dashboard, Slack, Microsoft Teams, the MCP server, the CLI, the API, the browser SDK, and from Linear and GitHub. Wherever it starts, it becomes the same kind of thread.
  • Real-time sync. When a thread updates — a new message, a streaming agent response, a tool call, an artifact — it updates for everyone viewing it. Open a thread in the dashboard that started in Slack, and you see the full conversation.

​
Visibility

Every thread has one of two visibility settings:
  • Private. Visible only to you. Use it for exploratory work and quick lookups.
  • Organization. Visible to everyone in your organization. This builds a searchable, shared record of investigations.
New threads are organization-visible by default, and the owner can switch a thread between private and organization at any time. There is no separate “public” visibility — public sharing is a snapshot mechanism, covered next.

​
Multiplayer

Because organization threads are visible to your whole organization, any member with access to the project can open one and add to it — asking follow-up questions or continuing where a teammate left off. Sazabi also tracks each person’s read position, so you can see where you are in a long thread. This makes threads a shared space for incident response and onboarding, not a single-person chat.

​
Sharing

There are two ways to share a thread, and they are different.
  • Internal link. Copy a thread’s link from the dashboard to send it to a teammate. The link respects the thread’s visibility — the recipient must have access to the project to open it. This is for sharing inside your organization.
  • Public snapshot. You can create a read-only public snapshot of a thread to share findings outside your organization. A snapshot is a frozen, allowlisted view — it does not expose your live thread or project. Create and revoke snapshots from the thread’s share dialog in the dashboard, or through the CLI and API (sazabi threads share create / list / revoke).
A public snapshot is readable by anyone with the link. Create one only for a thread whose contents are safe to share externally, and revoke it when you no longer need it.

​
Forking

Fork a thread to branch off from a specific message and explore a different hypothesis without disturbing the original. The fork is a new thread that starts from the point you chose. Fork from the message actions in the dashboard, or with sazabi threads fork from the CLI.

​
Search your history

Your threads are searchable, so past investigations stay useful.
  • From the dashboard. Open the command palette and search — matching threads appear as you type.
  • From the CLI and API. Use sazabi threads list to browse and sazabi threads search "<query>" to find threads by content.

​
Organizing and archiving

  • Pin threads you return to often so they stay at the top of your sidebar.
  • Archive threads you no longer need, to keep the sidebar clean. Archiving is a listing state, not deletion — archived threads stay searchable and can be reopened. Manage them under Settings > Archived threads.

​
Further reading

Chat from your messaging platform

Start threads from Slack or Microsoft Teams.

Agent tools

What the agent can search and do in a thread.