Keeping Memory Healthy: vem summarize, diff, and doctor

Your codebase changes every day. Without maintenance, .vem/CONTEXT.md starts describing architecture that no longer exists, CURRENT_STATE.md refers to tasks that were finished weeks ago, and agents confidently give wrong answers based on outdated facts.

vem provides three focused tools to combat this: summarize detects new changes and proposes memory updates, diff shows you what has drifted from the cloud, and doctor checks the overall health of your memory setup.

vem summarize analyses your recent git log and compares it against your current .vem/ content. It then proposes targeted updates — new changelog entries, task status changes, and context refreshes — based only on what actually changed.

Run it after a big merge or at the start of a new sprint to quickly catch up your memory to the current state of the code.

Every vem push sends a snapshot to the cloud. vem diff compares your current local .vem/ state against the last verified cloud snapshot, showing you exactly what is out of sync.

This is especially useful before pushing — you can review the diff to make sure you are not overwriting important cloud-side changes made by a teammate.

vem doctor runs a comprehensive diagnostic across your entire setup: authentication status, project configuration, git integration, local .vem/ data integrity, and cloud sync status. It reports each check as pass, warn, or fail with actionable suggestions.

Make it part of your onboarding checklist for new team members and your first step whenever something feels off.

The most effective teams build a two-minute memory check into their workflow: run vem doctor at the start of a sprint to confirm everything is wired up, vem summarize after landing a significant PR, and vem diff before any vem push. This takes less time than writing a Slack update and keeps every agent — human or AI — working from accurate context.