Organizational Memory
Codumentor can build and maintain a shared knowledge base from conversations across your team. Insights, conventions, decisions, and patterns are automatically captured, deduplicated, and surfaced when relevant.
This feature may not be available in all setups. If you don't see memory cards in your conversations, it may not be enabled by your administrator.
How it works
- Automatic extraction — After each conversation, a background process analyzes the exchange and extracts useful insights (naming conventions, architectural decisions, workarounds, etc.)
- Deduplication — The system checks if similar knowledge already exists and updates or merges rather than creating duplicates
- Retrieval — Before the assistant answers your question, it searches the knowledge base for relevant entries and uses them as context
- Version control — All knowledge is stored as Markdown files in a dedicated git repository, with full history and diffs
Rapid Direction Cues
When the assistant finds relevant knowledge, it receives these as Rapid Direction Cues — brief, contextual hints injected before it responds. You may see references to these in the assistant's answers, such as "Based on existing team knowledge..." or similar phrases.
This means the assistant's answers are grounded in what your team actually knows and has decided, not just generic patterns.
Voting and feedback
When the assistant surfaces a memory, you'll see voting controls:
| Action | Effect |
|---|---|
| Like | Reinforces the memory — it will be prioritized in future retrieval |
| Dislike | Signals the memory may be wrong or unhelpful — provide a reason if possible |
| Flag | Escalates the memory for human review |
Your votes directly improve the knowledge base for everyone on the team.
Memory cards
Memory-related activity appears as cards in the conversation transcript:
- Memory stored — a new insight was extracted and saved
- Memory retrieved — existing knowledge was found and used to inform the response
These cards show summaries of what was stored or retrieved.
Confidence and seniority
The system assigns confidence scores to memories based on the author's role. More senior contributors' insights are weighted higher in search results. This happens automatically — you don't need to configure anything.
What gets stored
The system extracts:
- Naming conventions and coding standards
- Architectural decisions and their rationale
- Undocumented workarounds and gotchas
- Cross-repository dependencies and relationships
- Historical context about why things were built a certain way
It does not store sensitive information like passwords, API keys, or personal data (though this depends on your organization's configuration).
Your own earlier conversations
This is a separate feature from the team knowledge base above, and a setup
may have either, both, or neither. The assistant can search and reread *your
own* past conversations — never anyone else's — when your question points back
at earlier work.
It happens two ways:
- When the assistant decides to look. Say "like last time" or "as we discussed", and it searches your history and rereads what it finds. A tool card appears in the transcript, and every result links to the conversation, so you can see exactly what it read.
- At the start of a turn. Before answering, it can look for your earlier conversations about the same thing and be handed a short list, with a card in the transcript naming what was offered. Most turns match nothing and show nothing — that is normal and deliberate: it speaks up only when a word in your question is distinctive enough to mean something in your own history.
Being offered a conversation is not the same as reading it. The list is a menu;
the assistant still has to open one, and is told the matches may be irrelevant.
Settings
Under Settings → Extensions:
| Setting | What it does |
|---|---|
| Recall earlier conversations automatically | Turns the start-of-turn look-up on or off. With it off, the assistant can still search your history when it decides to. |
| How eagerly to recall | Focused speaks up only on strong matches; Balanced is the default; Broad brings up more, and is wrong more often. |
| Where to look | Stay inside the workspace you are working in, or search across all of yours. |
Your own conversations only, always: recall never reaches another person's
history, and a conversation you deleted stays deleted. If you do not see these
settings, your administrator has not enabled the feature.