面试题库

30 天从前端工程师到 Agent 工程师

D6 消息、上下文工程与压缩、会话存储/恢复/分叉（dg M06/M08/M09/M10）

• 短期上下文和长期记忆的边界怎么划？一条信息该往哪放，你的判断依据是什么？Where do you draw the line between short-term context and long-term memory, and how do you decide where a given fact belongs?

  国内高频海外高频基础#memory#context-engineering

  分析过程 · 先想清楚再作答

  1. 这题看着像概念题，其实考的是你有没有一条可执行的判据。背出「短期在 messages 里、长期在向量库里」只是描述现状，答不出「为什么这条该进长期」就没有区分度。
  2. 先把两者的工程属性摆出来，边界自然就清楚了：短期上下文随会话结束作废、全量进请求、按 token 计费、受窗口约束；长期记忆跨会话存在、不进请求而是检索后注入、按条存储、受检索质量约束。
  3. 给一条可复用的判据，这是本题的核心：问三句话——跨会话之后还需要吗、会随时间失效吗、能通过检索捞回来吗。三个都是「是」就进长期记忆，第一个是「否」就留在短期。举例说明：用户住上海进长期，用户刚才让我把段落改成三句话留短期。
  4. 点出最常见的误用：把长期记忆当上下文一次性全塞进去。用了半年攒两百条偏好，全塞进请求既撑爆窗口，又因为大量不相关记忆干扰模型判断——长期记忆的价值在于按需检索出最相关的三五条，不在于存了多少。
  5. 可以预期的追问：长期记忆怎么更新和失效？答要点是记忆要带时间戳和来源，用户改了主意要能覆盖旧记忆而不是并存两条矛盾的；再补一句删除权——用户要求删数据时，长期记忆是必须能定位并整体删掉的那一部分。

  How to reason about it · think before answering

  1. This looks conceptual but is really asking for an operational test. Reciting 'short-term lives in messages, long-term lives in a vector store' just describes the status quo and gives no signal.
  2. Lay out the engineering properties and the boundary draws itself: short-term context dies with the session, ships in full on every request, is billed per token and capped by the window; long-term memory spans sessions, is retrieved and injected rather than always sent, is stored per item and capped by retrieval quality.
  3. Give a reusable test — this is the core of the answer. Ask three questions: is it still needed after this session ends, does it expire with time, can retrieval find it again? Three yeses means long-term; a no on the first means it stays short-term. Illustrate: 'the user lives in Shanghai' is long-term, 'the user just asked me to shorten that paragraph to three sentences' is not.
  4. Name the common failure: stuffing all long-term memory into the prompt. Two hundred preferences accumulated over six months will both blow the window and drown the model in irrelevance. The value of long-term memory is retrieving the three or four relevant items, not the volume stored.
  5. Expect the follow-up on updates and expiry: memories need timestamps and provenance, and a changed preference must overwrite rather than coexist with a contradictory one. Add the deletion angle — long-term memory is the part you must be able to locate and erase when a user asks for their data to be deleted.

  答题要点

  • 短期上下文随会话作废、全量进请求、按 token 计费受窗口约束；长期记忆跨会话、按需检索后注入、按条存储受检索质量约束
  • 判据三问：跨会话还需要吗、会随时间失效吗、能被检索捞回来吗——三个都是就进长期记忆
  • 常见误用是把长期记忆整包塞进上下文，既撑爆窗口又用不相关的记忆干扰模型，正确做法是检索最相关的三五条
  • 长期记忆要带时间戳和来源，用户改主意时覆盖旧记忆，避免两条矛盾记忆并存
  • 长期记忆是合规上必须能按用户定位并整体删除的那一部分，短期上下文随会话删除即可

  Key points

  • Short-term context dies with the session, ships in full, and is billed per token under the window cap; long-term memory spans sessions, is retrieved on demand, and is capped by retrieval quality
  • The three-question test: is it needed after this session, does it expire, can retrieval find it — three yeses means long-term
  • The common failure is injecting the whole memory store, which blows the window and drowns the model in irrelevance; retrieve the three or four relevant items instead
  • Long-term memories need timestamps and provenance so a changed preference overwrites the old one instead of contradicting it
  • Long-term memory is the part that must be locatable and deletable per user for compliance, while short-term context simply dies with the session