Correction Workflow
How to inspect, edit, and verify a wrong memory in MemexAI.
Wrong memory should be fixed at the record layer. MemexAI stores durable memory as inspectable files, so an operator can correct the source that future prompt blocks and memory searches will read.
1. Find the memory
Open the admin UI at /admin, choose the affected user, and inspect the Files view. User-scoped memory appears under physical paths like:
users/{userId}/profile.md
users/{userId}/preferences.md
users/{userId}/projects/current.mdIf you know the agent-visible path, translate user/profile.md to users/{userId}/profile.md.
2. Check the trail
Before editing, review:
- The current file content
- Recent revisions for that file
- Access logs showing which tool read or wrote it
- The actor and reason fields, when present
This helps separate a model misunderstanding from a stale or incorrect durable record.
3. Edit the file
Open /admin → Files → navigate to the user's file → click Edit.
Paste the corrected content in the editor and fill in a short reason such as corrected user neighborhood preference after support review. Click Save.
The edit creates a normal mx_revision row. Previous content stays visible in the Revisions view.
For deletion or privacy requests, do not rely on editing alone. Delete or purge matching rows from mx_file, mx_revision, and mx_access_log according to your retention policy.
4. Verify the next prompt block
Open /admin → Files → select the corrected file and confirm the content reflects the fix. On the next user session, the updated file will be injected into the prompt block automatically.
To check immediately, open the Tool Playground, set the user ID, and run memory_context with a query that touches the corrected field. Confirm the corrected fact appears in the result.
5. Run a two-turn check
Ask the agent a question that depends on the corrected memory. Check that the corrected fact is present in context and used by the agent without requiring the user to restate it. Treat failures as prompt or tooling regressions to investigate.
For higher-risk products, keep a small regression script with the exact correction scenario so the team can rerun it after changes to prompts, adapters, or memory tooling.
When to delete instead of edit
Delete or blank a memory file when the fact should no longer be retained at all. Edit when the fact is still useful but wrong, stale, or too vague.
If your app has compliance deletion requirements, handle account-level deletion in your application workflow and include MemexAI's mx_file, mx_revision, and mx_access_log data in that process.
Dreaming interactions
Dreaming writes through normal memory tools and creates normal revisions. If you correct memory while dreaming is enabled, inspect the next dream-agent revision for that user. Pause dreaming for that user during sensitive manual review if needed.
See Background Dreaming for pause controls.