Three ways to build knowledge
/learn: Explicitly capture facts from a thread or provide them directly. The most common way to add knowledge.- Knowledge proposals: After a run, Slack Agent may offer to save durable facts it discovered. Public channel proposals can auto-apply; private channels require confirmation.
- Background curation: A weekly workflow refreshes existing knowledge from connected upstream systems automatically.
Public vs. private knowledge
Knowledge boundaries follow Slack privacy boundaries.| Slack surface | Knowledge behavior |
|---|---|
| Public channels and shared surfaces | Use the global workspace Knowledge Base |
| Private channels | Use a private conversation Knowledge Base |
| DMs and group DMs | Use a private conversation Knowledge Base |
Think of the global Knowledge Base as shared memory and private conversation knowledge as an isolated overlay with selective shared context available for reference.
Capturing knowledge with /learn
Use /learn to capture anything worth keeping: architectural decisions, operational facts, team conventions, or clarifications that would otherwise be lost. For example:
Whatโs next
Working in Slack
See how
/learn fits into normal Slack workflows.Thread reviews
Inspect the run details and artifacts behind a conversation before deciding what knowledge should be preserved.
Knowledge Base overview
Read the broader CodeRabbit docs for how Knowledge Base concepts work across the product.