Background Learning: When It Should Stay Off

Skill Workshop can learn procedures from what you already did. Official v2026.10.5 notes: background learning sends conversation and tool content to your configured model provider and can add usage charges. Choose Off to stop background learning and unused-skill cleanup; you can still request learning with /learn.

How to inspect and Undo a learned skill is on Skill Workshop 2.0. This page is the cost and privacy choice.

Leave it Off when

  • The thread includes customer mail, tokens, or paths you would not paste into a cloud model.
  • You already pay for tool-heavy Opus/Sol runs and do not want a second silent pass.
  • Several people share one Gateway: one person’s “how I deploy” should not become a skill for everyone.

Use /learn instead

When a procedure is worth keeping, run an explicit learn after you have stripped secrets from the thread. Then open Workshop, compare versions, and pin the good one. Check the drip on 30-day Usage the next day.

Cleanup follows Off

Turning background learning Off also stops unused-skill cleanup in that 10.5 note. Do not expect the product to prune stale learned skills while learning is Off. Archive in Workshop if you want them out of the way without deleting history.

Related