Tencent-Hunyuan/Hy-Memory

Maintainer? Show your league in your README

Card: your league's emblem, from Copper to Legendary

[![bestofgithub](https://bestofgithub.dev/badge/Tencent-Hunyuan/Hy-Memory.svg?style=card)](https://bestofgithub.dev/repo/Tencent-Hunyuan/Hy-Memory)

Flat: fits beside your other badges

[![bestofgithub](https://bestofgithub.dev/badge/Tencent-Hunyuan/Hy-Memory.svg)](https://bestofgithub.dev/repo/Tencent-Hunyuan/Hy-Memory)

Loading README…

`scene`	Tasks	Memory shape
`chat`	Small talk, personal information, preferences, general Q&A	Hierarchical memory (L0–L7)
`working`	Productivity work: documents, spreadsheets, research, financial analysis, content creation, computer operation	Two-layer memory: session facts + reusable experiences
`coding`	Software engineering: coding, debugging, testing, builds, APIs/SDKs, scripts, SQL	The same two-layer memory as `working`, plus a code version-evolution chain (diff chain)

Layer	Name	Content
L0	`BASIC_INFO`	Basic information
L1	`RAW`	Raw conversation (append-only)
L2	`FACT`	Atomic facts (versioned, immutable records)
L3	`SUMMARY`	Session summaries
L4	`IDENTITY`	Reserved
L5	`KNOWLEDGE`	Reserved
L6	`SCHEMA`	Mental models (abstract narrative templates, graph layer)
L7	`INTENTION`	Prospective intentions (with an expiry; demoted to ordinary facts once expired)

Mode	What it does	Graph DB	Use case
`lite`	Raw-only embedding writes and searches, no LLM calls; `scene` and `layers` are ignored	No	Vanilla vector RAG, fast ingestion, zero LLM cost
`pro`	+ LLM extraction + reconcile	Optional (`MEMORY_ENABLE_GRAPH`, off by default)	Standard workloads
`ultra`	+ System 2 schema induction + cross-domain sweeper (triggered by `evolve()`)	Yes (always on)	Full cognitive architecture

Layer	What it records	Per session	Structure
Facts (`WorkingFact`)	What this session did: the task, the approach, the result	Exactly 1, no threshold	`statement`, `subject`, `files`, `details` (verbatim source)
Experiences	Approaches that can be reused next time a similar task comes up	0–N, must pass a value threshold	`task`, `search_keys`, `solution`, `boundary_envs`, `confidence`

	Working	Coding
Extraction spec	Productivity-task spec	Software-engineering spec: the subject must be code or a decision; record exact coordinates (file / function / branch) instead of pasting code
Storage	`coding_memory.db` + `_coding_keys` / `_working_facts` collections	`coding_memory_cv.db` + `*_cv` collections, fully isolated from working
Version-evolution chain	None	Yes: how many times the same code was changed, and what each change was

Hy Memory