Keep each piece of work in a thread
Every piece of work in Sidekick happens in a thread. A thread keeps the information you need to understand and continue that work:- The conversation, and who took part in it.
- The tool runs that were requested, and what they returned.
- The approvals that were asked for, who granted them, and when.
- The files that went in and the artifacts that came out.
- The model and execution history behind each turn.
Shared work, not isolated chat
Sidekick is built around shared work. Threads can live in Rooms with people, files, connectors, and shared starting context, then be continued without rebuilding the background from scratch. The company controls which tools are available, which models are approved, and which actions need sign-off. That control is part of the product, not bolted on around it.Start your first thread
Open a thread, pick its tools and model, run the work, and review the result.
Understand governance
See how user and administrator approvals control sensitive actions.
Customize tools and connectors
Add approved tools, connectors, and reusable skills to a thread.
Plan a rollout
Bring Sidekick to a team or the whole company with a staged plan.
Read the concepts first
These pages set the mental model for everything else in the documentation.Terminology
The core vocabulary: thread, Room, artifact, skill, connector, Harness, and more.
How work runs
Choose a Harness and decide where Sidekick should run the work.
How models are chosen
Auto Route, approved catalogs, admin defaults, and bring-your-own providers.
Web, desktop, and Slack
One product across web, desktop, and Slack, with the same thread record.