Use Sidekick in a project

Ask a focused question

1. Open the target projectSelect Sidekick from that project dashboard.

   Its answer and history stay project scoped.
2. Ask for an object and decisionMake the intended outcome explicit.

   For example: “Which knowledge sources need attention, and why?”
3. Watch the read progressA row such as Using List Datasources means it is retrieving permitted data.

   It does not make a change.
4. Use the answer or review a proposalFollow linked dashboard work; approve a proposal separately.

   A proposed change never runs from the chat text alone.

Understand a thread

A thread is your Sidekick conversation history for one project. Threads are owned by the signed-in user, scoped to the project and workspace, and shown in recent-first order. Starting a new panel conversation creates a thread when you first send a message. A thread is active while it can receive messages; it is not shared with other users just because they belong to the workspace.

Each successful message refreshes the thread's retention window. The service default is 90 days, but retention can be configured by the deployment. Do not use a Sidekick thread as the system of record for approvals or operational history.

Delete Sidekick history

1. Open the project’s Sidekick panelSelect the trash icon in the open panel.

   The action applies to your stored Sidekick history in this project, including the current session.
2. Read the scope and confirmSelect Delete history only when you intend to remove all of that project-scoped history.

   This is permanent and cannot be undone.

The panel deletes the stored conversation checkpoints before recording the threads as deleted. On success it clears the local panel and begins a new project-scoped conversation. This is permanent and cannot be undone.

Last updated on