JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(profiles): make user-profiles guide and notebook user-only

Browse Source 
Remove leftover agent and regenerate references so the docs match the shipped
v1 SDK: drop the entity_type settings argument and the agent entities example
from the guide, and remove the regenerate demo section and cheat-sheet row from
the notebook.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
karthik
2026-09-23 19:53:41 +05:30
co-authored by Claude Opus 4.8
parent d91d793c52
commit f29820886a
2 changed files with 9 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/platform/features/user-profiles.mdx
+3 -5
View File
@@ -281,10 +281,9 @@ On a project where profiles are turned off, a read returns `status: not_enabled`
| `enabled` | boolean | Whether profile generation runs for the project |
| `schema` | object | JSON Schema describing the profile. Every property needs a `description` |
| `custom_instructions` | string | Extra guidance applied during extraction |
| `entity_type` | string | Which entity kind `schema` and `custom_instructions` apply to. Defaults to `user` |
`enabled` is project-wide. `schema` and `custom_instructions` belong to one
entity type, so the stored settings nest them under `entities`:
`enabled` is project-wide. `schema` and `custom_instructions` apply to user
profiles, so the stored settings nest them under `entities`:
```json
{
@@ -293,8 +292,7 @@ entity type, so the stored settings nest them under `entities`:
"user": {
"schema": { "type": "object", "properties": { "...": {} } },
"custom_instructions": "Prefer durable traits over one-off remarks."
},
"agent": { "schema": null, "custom_instructions": null }
}
},
"capabilities": { "full_rebuild": false }
}