Lessons are off for every organization until crewkit turns them on for it, and only on the Team, Business and Enterprise plans. After that, an organization admin or owner gives the two consents in Turning Lessons on. Until crewkit turns them on, the Lessons settings do not appear and every Lessons screen is empty.
A Lesson is a short rule a person on your team wrote or approved, after the same kind of evidence came up for two or more people on a project: a mistake caught in their sessions, a pull request review comment the author acted on, or a confirmed meeting, Slack or email document. Once accepted, crewkit adds it to later Claude Code sessions on that project, so the next session starts with what the team already learned.
Turning Lessons on
Two organization settings control Lessons. Both are off by default, and each is a separate consent. An organization admin or owner turns them on and off in Settings → Organization → Privacy & Telemetry, in the Lessons section.
| Setting | What it allows |
|---|---|
| Propose Lessons from repeated corrections | crewkit proposes a Lesson when the same kind of mistake recurs on the same file for two or more people. |
| Add accepted Lessons to sessions | Accepted Lessons are added to later sessions on the same project, and an agent can read them through the MCP get_lessons tool. |
Turning either one on asks you to confirm, and the confirmation restates what the acceptable-use policy says about Lessons. The acceptable-use policy describes both settings. Editing, accepting, rejecting or retiring a Lesson, and the get_lessons read, need the signed-in person to have accepted the current version of the policy.
Where a proposal comes from
With the first setting on, crewkit proposes a Lesson from three kinds of evidence:
- Corrections a person or a reviewer caught. These come from correction detection, from conversations that are not sensitive, not deleted, and not attributed to a private repository. A private repository never seeds a Lesson.
- Pull request review comments the author acted on. A comment by someone other than the pull request's author, and not a bot, followed by a commit to that pull request. The pull request must be a confirmed document in the project.
- Confirmed meeting, Slack and email documents. Only documents a person has confirmed for use in sessions.
A Lesson is proposed only when the same kind of evidence recurs on the same file for . One person's mistakes never become a Lesson on their own.