# Capturing from Conversations
Answers worked out in conversation are easy to lose. When a Q&A or troubleshooting session settles something worth keeping, ask the Agent to capture it. What you bring becomes a source, the Agent plans which pages it affects, and the normal update flow turns it into reviewed knowledge.
```mermaid
flowchart LR
qa["Q&A or discussion"] --> keep{"Worth keeping?"}
keep -->|yes| src["Save as a source
summary / document / code / MR"]
src --> plan["Agent proposes
affected pages"]
plan --> upd["Update and Review"]
upd --> kb["Approved knowledge"]
```
## What can become a source
| You have | It becomes |
| --- | --- |
| The conclusions of this conversation | A [session summary](), optionally linked to commits or merge requests |
| Text you paste or an excerpt you hold | A [note]() |
| A new document | A [document]() or [Lark]() source, captured |
| Specific code or a merge request | An update of the registered [repository]() to the merged commit |
```text
That explanation of the retry limits is right. Save this conversation as a
session summary linked to the merge request, and update the affected pages.
```
## What the Agent does
1. Saves the material. A conversation is summarized — the problem, confirmed decisions, reasons and open questions — never stored as a transcript.
2. Proposes a plan: which existing pages to revise and whether a new page is warranted. A new topic goes through structure review first.
3. Runs the update with the saved source in the affected pages' scope, and brings the changed pages to Knowledge Review.
Saving a source alone starts no knowledge work, so you can also save now and update later. A summary that arrives after the code was already processed can still update a page; the code version is reused, not re-parsed.
## When a question finds a gap
When querying shows that the knowledge is missing or out of date, the query Skill suggests an update with the affected page, the proposed change and the source scope — and starts nothing until you accept. On acceptance it hands the evidence to the production entry in the selected Context knowledge workspace. See [Asking Questions]().
## Boundaries
- Only material you supply or authorize is captured; the Agent does not scan its own history.
- A linked merge request records an association; it does not prove the change was merged or tested.
- Saving a conversation or approving knowledge does not approve any upstream change discussed in it.
---
## Sources
- note:20261012/knowledge-service-agent.md · knowledge-service-agent.md L47–L47
- [context/packages/context/docs/guides/sessions.md L3–L8 · 3b0ce0a]()
- [context/packages/context/docs/guides/sessions.md L22–L29 · 3b0ce0a]()
- [context/packages/context/docs/getting-started.md L71–L74 · 3b0ce0a]()
- [context/packages/context/docs/guides/sessions.md L10–L15 · 3b0ce0a]()
- [context/packages/context/docs/guides/knowledge-updates.md L450–L457 · 3b0ce0a]()
- [context/packages/context/docs/guides/knowledge-updates.md L492–L497 · 3b0ce0a]()
- [context/plugins/context/skills/context-inspect-search/SKILL.md L462–L471 · 3b0ce0a]()
- [context/packages/context/docs/guides/sessions.md L25–L26 · 3b0ce0a]()
- [context/packages/context/docs/guides/sessions.md L48–L49 · 3b0ce0a]()