User Profiles

Profiles are durable facts about a user and their environment. They help an agent personalize future responses without replaying the full interaction history.

Examples include preferences, goals, constraints, role information, data conventions, and stable workflow context. Behavioral instructions for the agent belong in playbooks instead.

Profiles vs. Interactions

Every profile keeps source attribution so you can trace it back to the request that produced it.

Lifecycle

1. Extract — eligible interaction windows produce profile candidates.
2. Consolidate — Reflexio merges duplicates and resolves overlapping facts.
3. Retrieve — semantic search returns profiles relevant to the current user query.
4. Revise — later evidence can replace an outdated profile while preserving lineage.
5. Expire or delete — time-limited or explicitly removed data leaves the active retrieval set.

Profiles are not a transcript cache. Prefer facts likely to improve a future response, and avoid extracting transient wording or behavioral instructions.

Retrieval

Profile retrieval is always user-scoped. Query with the current user message or a concise description of the context the agent needs. Tags and source filters can narrow retrieval when your application maintains stable categories.

Use unified search when the agent needs both profiles and playbooks in one call. Use profile search when you only need user memory or are debugging profile extraction.

Configuration

Reflexio includes a default profile extractor. Customize it only when your domain needs a narrower definition of durable memory. One organization has one active profile extractor; the extractor can be disabled, set to manual mode, filtered by request source, or given window overrides.

For implementation patterns, see Working with User Profiles. For exact fields and methods, see the Profile API Reference.