viettranx 558bdd6d5c fix(memory): use per-user workspace for memory path detection and KG extraction ...

Two related fixes:

1. Memory interceptor now resolves workspace from request context
   (per-user workspace) instead of using the static global workspace.
   This fixes memory writes with absolute paths under per-user
   workspaces (e.g. workspace/channel/userID/memory/) being bypassed
   and written to disk instead of the database, which also prevented
   KG extraction, memory indexing, and cross-session recall.

2. KG extractor: increase max_tokens 4096→8192, add retry on
   truncation (finish_reason=length), and support chunking for
   long inputs with deduplication on merge.

2026-03-13 13:22:02 +07:00

..

extractor_prompt.go

refactor(kg): improve extraction prompt with few-shot example and controlled vocabulary

2026-03-12 18:54:14 +07:00

extractor.go

fix(memory): use per-user workspace for memory path detection and KG extraction

2026-03-13 13:22:02 +07:00