Work and content
| Term | Definition |
|---|---|
| Thread | A durable ledger for one piece of work. It holds the conversation, participants, tool runs, approvals, files, artifacts, and execution history together, and it stays replayable. |
| Project | A grouping of related threads and files that share context, so work in one place does not have to be rebuilt in another. |
| Artifact | A durable output produced inside a thread, such as a document, dataset, or file, kept with the thread that created it. |
| Skill | A reusable, named piece of work Sidekick can run on request or on a schedule. It uses the same tool and policy controls as an interactive thread. |
| Memory | Durable user context Sidekick can recall across threads when it is enabled. Facts can be saved or corrected, and recall respects the same controls as any other read. |
Tools and models
| Term | Definition |
|---|---|
| Connector (tool) | A governed capability a thread can call, such as reading from or writing to an external system. Availability depends on workspace configuration, approval, access, and policy. |
| Harness | The agent engine that runs a thread: the loop that reasons, calls tools, and produces output. |
| Auto Route | The default model behavior, where Sidekick picks a model for each turn from the approved catalog. See How models are chosen. |
| Approved catalog | The set of models an admin has allowed for a workspace. A person can pick a specific model from this set, or let Auto Route choose. |
Execution
| Term | Definition |
|---|---|
| Placement | Where a thread’s work runs. There are two: cloud (a managed remote environment) and on your computer (an approved desktop device). See How work runs. |
| Cloud | The default, always-available placement. Work runs in a managed remote sandbox. |
| On your computer | A placement where work runs on an approved desktop device. It requires the desktop app and admin enablement. |
Governance
| Term | Definition |
|---|---|
| Consent gate | The checkpoint an external or sensitive tool call passes through before it runs. You can allow it once, for this thread, or always. See Governance model. |
| Approval | An additional sign-off some tools require from a workspace admin before they run. After approval, the person resumes the work themselves. |
| Schedule | A trigger that runs a skill at a set time or on a defined event. Scheduled runs use the same tool and policy controls as interactive work. |
| Nudge | A prompt from the desktop app that brings relevant work back to a person at the right moment. |
People and boundaries
| Term | Definition |
|---|---|
| Workspace | The company-controlled boundary that owns threads, configuration, approved tools and models, and audit history. |
| Member | A person who uses Sidekick to do work within a workspace. |
| Admin | A person who governs a workspace: sets model defaults, approves tools, enables placements, and reviews audit history. |