agenta memory eklendi
CI / test (pull_request) Successful in 2m31s

This commit is contained in:
deniz committed 2026-09-24 04:04:03 +03:00
1 parent 45e913bd10
commit 2eb79f3400
14 files changed
+1523 -18

No files matched your search

+28
View File
@@ -644,6 +644,34 @@ next hourly prune:
llmgw keys threads --project default --off
```
## Memory notes for agents
Also off until a project asks, for the same reason. Where conversations are what
was said, notes are what an agent chose to keep, and they persist across
conversations:
```
llmgw keys memory --project default --retain-hours 720
```
The retention is required and is measured from the last write to a note. An agent
then saves, searches and deletes notes through `/v1/memory` or, as tools, through
the MCP server at `/mcp` (`remember`, `recall`, `forget`). Both need the API key
of the project, and notes are private to the project and to the agent id sent in
`x-llmgw-agent`. A note in another project or agent answers the same as one that
does not exist. llmgw does not add these tools to requests itself.
Turning it off stops new storage, and existing notes go at the next hourly
prune:
```
llmgw keys memory --project default --off
```
Without authentication, `threads.store` and `threads.retain_hours` in
`server.yaml` keep both conversations and notes in one shared pool. That is for
one trusted machine only; see [quickstart.md](quickstart.md).
## Reclaiming disk
`llmgw ctl nodes` has a DISK column: free space against the size it is free