Skip to main content
Sidekick is the AI application your company owns. People do real work with AI here, and the record of that work stays with the company, not inside one model provider’s app.

​
The one idea: a thread is a durable ledger

Every piece of work in Sidekick happens in a thread. A thread is not a throwaway chat window. It is a durable ledger that keeps everything about a task in one place:
  • 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.
Because the thread holds all of this together, work is replayable. You can reopen a thread weeks later and see exactly what happened and why. The thread is not tied to any one model provider’s application, so changing the model, or moving where the work runs, never scatters the record.

​
Shared work, not isolated chat

Sidekick is built around shared work. Threads can be grouped into projects, shared with collaborators, and continued without rebuilding context 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 consent gates and admin approval keep external and sensitive actions in bounds.

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, project, artifact, skill, connector, harness, placement, and more.

How work runs

Harnesses, placements, and why the thread stays the record wherever work executes.

How models are chosen

Auto Route, approved catalogs, admin defaults, and bring-your-own providers.

Surfaces

One product across web, desktop, Slack, and Teams, with the same ledger everywhere.