---
source: crewkit documentation
url: https://crewkit.io/docs/sensitive-sessions.md
title: "Sensitive sessions"
description: "What starting a session with --sensitive changes, what it does not change, and how resuming a conversation affects it."
---


A sensitive session is one you start with `crewkit code --sensitive`. It keeps the conversation to yourself and out of crewkit's analysis and search. It does not keep it off crewkit's servers.

---

## What `--sensitive` does

- **Only you can find or open the conversation.** Managers, Admins and Owners cannot, and no one else can create a share link for it.
- **It is left out of crewkit's analysis:** session analysis, project search, correction detection and convention override resolution never run on it.
- **On your machine, the CLI turns off** the LLM gateway, OpenTelemetry per-request records, session summaries, and prompt-driven document search for that session, and Lesson search when Lessons is on. In `crewkit tui`, plans still show in the sidebar on your machine, but that session's `crewkit tui` uploads none of them. A plan it writes can still be uploaded by another, ordinary `crewkit tui` running on the same machine.
- **The MCP search tools send no query:** `search_project_context`, `find_prior_work` and, when Lessons is on, `get_lessons`.
- **Some MCP tools refuse outright:** `add_note`, `save_state`, `share_update`, `channel_create`, `propose_feedback_triage` and `resolve_feedback`.

## What it does not do

- **It does not stop crewkit from storing the session.** In an organization crewkit hosts, the transcript and hook events are still sent and stored under your organization's [capture mode](/docs/capture-modes). In a [resident organization](/docs/data-residency), a sensitive session's content goes nowhere.
- It does not change the capture mode or the retention term.

---

## Resuming a conversation

A launch that continues a conversation without naming it by its id (`crewkit code -r <name>`, `crewkit code -c`, the resume picker, or a fork with `--fork-session`) cannot tell at launch whether that conversation is sensitive. For the whole of such a launch, the three MCP search tools send no query and answer with one fixed sentence saying crewkit did not search. The same holds when you resume a sensitive conversation by its id without `--sensitive` (crewkit answers at launch that the conversation is sensitive, and the session's Bash tool is then treated as sensitive too), and when a resume could not register its session with crewkit. To keep the search tools on an ordinary conversation, resume it by its id: `crewkit code -r <session id>`. Run from a session launched with `--sensitive`, or one resumed by its id into a conversation crewkit answers is sensitive, `crewkit blueprint create` searches no documents with its input and does not upload the plan (`--dry-run` still shows it), `crewkit work start <description>` sends the description to no tracker search, and `crewkit work start <KEY> --title` and `crewkit work update <handle> --title` refuse the title and send nothing (start from the card key alone, or set the title from an ordinary shell). On a launch onto a conversation it cannot name, the session's own commands are not treated as sensitive, so those commands still send.

---

## Next steps

- [Capture modes](/docs/capture-modes)
- [Data residency](/docs/data-residency)
