You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(session): persist metadata + inject into memory extraction prompt (#2414)
Sessions can now carry an arbitrary metadata dict (project name,
tech-stack preferences, architectural style, etc.) that survives
through commit and is included in the system context the memory
extractor sees. Today the only way to express project-level
personalization was to allocate a separate agent_id per project; with
this change, a single agent can keep distinct memory layers across
projects via session metadata.
- Session model + storage gain a metadata field (dict, JSON-serializable,
size-capped at 16 KB, key-count-capped at 64).
- API: POST /api/v1/sessions accepts metadata; PATCH
/api/v1/sessions/{id}/metadata merges by default, replace=true overrides.
- Memory extractor: when metadata is present, a [Session metadata] block
is added to the prompt's system context.
- CLI: ov session set-metadata --key K --value V.
Closes#2414
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments