Session Summaries

Design discussions, troubleshooting sessions and requirement conversations with an Agent often settle things that no document records. A sessions source keeps a bounded summary of such a conversation so that pages can cite it. It is a summary, never the transcript: Context does not scan your Agent's history or ingest a whole conversation.

What to keep

The Agent (or whoever supplies the summary) prepares it before import:

Keep	Drop
The problem, confirmed decisions and the reasons that matter	Repetitive turns
Constraints and open questions	Tool logs
Whether each statement was proposed, agreed, implemented or verified	Abandoned attempts, unless they explain a current limit

If only a supplied summary exists, the source says so. Speakers, dates and approvals are never made up, and a conversation with nothing reusable can stay out of the Context knowledge workspace.

Save it

Ask at the end of the conversation:

Summarize what we decided about retry limits and save it as a Context
session summary, linked to the merge request we just opened.

The Agent imports a payload like this with context source import --input <file>:

type: sessions
name: 20261012/retry-limits.md
markdown: |
  # Retry limits for payment callbacks
  ...
changes:
  - mr: https://git.example.org/team/payments/merge_requests/42

Use the actual conversation date, or the collection date if unknown, and keep the same name for later corrections. The optional changes field links one or more code changes: each row takes a full commit SHA, an mr URL, or both, plus an optional repository. Omit it for a discussion with no code. A link records an association; it does not prove the change was merged or tested, and it does not authorize fetching the code.

How it is used

Saving starts no knowledge work. A summary that opens a new reader topic goes through the normal structure review and writing; one that only supports an existing page joins that page's reading scope while the page keeps its primary source. Either way, knowledge turns the conclusions into answers, explanations and procedures — not a meeting recap — and knowledge/structure.yaml records which sections cite the summary.

See Capturing from Conversations for the end-to-end flow after a Q&A.

Corrections

Correct a faulty summary by importing it again with its current base_digest; existing changes are kept unless you remove them, and changes: [] clears them. If the summary is accurate but a page is wrong, revise the page instead. Neither saving a summary nor approving knowledge approves the upstream code change it mentions.

会话摘要

与 Agent 进行的设计讨论、问题排查和需求沟通，常常会敲定一些没有任何文档记录的事情。sessions 来源会保存这类对话的一份有边界的摘要，供页面引用。它是摘要，绝不是完整记录：Context 不会扫描你的 Agent 历史，也不会摄入整段对话。

保留什么

Agent（或提供摘要的人）会在导入前准备好摘要：

保留	舍弃
问题、已确认的决定以及关键理由	重复的对话轮次
约束和未决问题	工具日志
每条陈述处于提议、已同意、已实现还是已验证状态	已放弃的尝试，除非它们能解释当前的某个限制

如果只有一份他人提供的摘要，来源中会如实注明。发言人、日期和批准情况绝不会被编造；没有可复用内容的对话可以不进入 Context 知识工作区。

保存

在对话结束时提出：

Summarize what we decided about retry limits and save it as a Context
session summary, linked to the merge request we just opened.

Agent 会用 context source import --input <file> 导入类似下面的载荷：

type: sessions
name: 20261012/retry-limits.md
markdown: |
  # Retry limits for payment callbacks
  ...
changes:
  - mr: https://git.example.org/team/payments/merge_requests/42

请使用对话的实际日期；若不清楚，则使用收集日期。后续更正时保持同一个名称。可选的 changes 字段用于关联一个或多个代码变更：每一行填写完整的 commit SHA、mr URL 或两者兼有，另可选填 repository。没有代码的讨论可以省略该字段。关联只记录一种联系；它不能证明变更已合并或已测试，也不授权抓取代码。

如何使用

保存不会启动任何知识工作。开启新读者主题的摘要会经过常规的结构审核和写作；只用于支撑现有页面的摘要会加入该页面的阅读范围，而该页面保留其主要来源。无论哪种情况，知识都会把结论转化为解答、解释和操作步骤——而不是会议纪要——并由 knowledge/structure.yaml 记录哪些章节引用了该摘要。

问答之后的端到端流程，参见从对话中采集。

更正

要更正有误的摘要，请带上其当前的 base_digest 重新导入；现有的 changes 会被保留，除非你删除它们，changes: [] 则会清空它们。如果摘要准确但页面有误，请修订页面。保存摘要和批准知识都不代表批准了其中提到的上游代码变更。