Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
Python agent-contextagent-memoryagent-pluginsagentic-ragcontext-databasedsh-pluginknowledge-basememorymemory-managementself-evolvingvector-database
fix(docs): link working-memory examples to GitHub (#5700)
Zayn Jarvis10f368145f43
diff --git a/docs/en/guides/working-memory-default-off.md b/docs/en/guides/working-memory-default-off.mdindex 1a2fd6261..7500de443 100644--- a/docs/en/guides/working-memory-default-off.md+++ b/docs/en/guides/working-memory-default-off.md@@ -86,7 +86,7 @@ that it depends on OV history. Middleware defaults to`include_session_context=False`. Put it before native summarization middlewareso raw messages are captured before the framework replaces them. Message capturewatermarks are persisted in graph state. See the runnable-[native history example](../../../examples/langchain-langgraph/langgraph/middleware/native_history.py)+[native history example](https://github.com/volcengine/OpenViking/blob/main/examples/langchain-langgraph/langgraph/middleware/native_history.py)and its pinned requirements for LangChain summarization with a SQLite checkpointer.VikingBot is an exception to the host-history default: it still uses OV Working@@ -99,7 +99,7 @@ confirm WM generation, the commit is treated as unsuccessful and local historyis kept for retry. This change does not replace VikingBot's local compaction.Some old OV-managed conversations no longer have a full host transcript. Stop-writes and use the [history export tool](../../../examples/session-history-export/README.md)+writes and use the [history export tool](https://github.com/volcengine/OpenViking/blob/main/examples/session-history-export/README.md)to prepare a new host conversation through its supported file/context input.Verify the host has the necessary history before continuing there. Export aloneis **not** an imported or verified migration; the tool never edits private host