AideAIHow Plan Remembers Your Workouts and Wellness Uses Them Later
Tuesday night you tell Plan:
I train three times a week—usually Monday, Wednesday, and Friday after class.
Plan helps you map the week around labs, readings, and recovery. Good. But on Thursday you open Wellness and want a lighter movement suggestion, not a lecture about time management.
Without shared memory, you would paste the same context again—or Wellness would guess.
This walkthrough shows how Personal Memory handles that gap: one stored fact, two agents, explicit boundaries.
Scene 1: Plan hears a stable habit
You are in a Plan thread, not Wellness. You mention a recurring routine in plain language:
I try to lift three times a week. M/W/F after 5 works best.
After Plan replies, AideAI finishes the turn and runs background extraction. Because this is a neutral, explicit first-person habit—not medical, not a secret—the app may auto-save it.
Under the assistant message you might see something like:
Saved: You train three times per week (Mon/Wed/Fri after class). Undo
You have ten minutes to undo if the wording is wrong. Undo rolls back that auto-save for this turn.
After you share a training rhythm in Plan, the reply can show Saved to personal memory, Undo, and other inline memory signals without opening Settings.
If the system is unsure, you get a confirmation card instead:
Save this to memory? with actions Remember, Edit, Don't save
Until you confirm, other agents do not receive the fact through shared memory.
Scene 2: Wellness opens on a different day
Two days later you start a Wellness chat:
I'm wiped after back-to-back classes. What's a realistic movement option tonight?
Wellness does not need Plan's full thread about deadlines, email drafts, or study blocks. It needs the relevant slice: you usually train three times a week, and tonight you want something lighter.
If Share memory between agents is enabled and the fitness/wellness domains allow retrieval, Wellness can use the stored fact in prompt context—subject to relevance scoring and limits—not because Wellness "read Plan's chat," but because the fact lives in your local profile with domain permissions.
Share between agents in Settings lets Wellness retrieve a fact Plan saved—without copying Plan’s chat history.
A helpful answer might reference your usual rhythm and propose a low-friction option for tonight, without asking you to restate your entire schedule.
If Wellness actually applies a stored fact, you may see Used from memory with a source hint (for example, saved via Plan). Simple retrieval without confirmed use stays in the access log only.
The Activity tab shows which memories were added to an agent’s context while preparing a reply—here Wellness can use a Plan-saved training habit without reading Plan’s chat.
Scene 3: The habit changes
Mid-semester your schedule shifts. You tell Plan:
I'm down to one gym session a week now—Sunday mornings.
Personal Memory treats an obvious correction as a new revision, not a silent overwrite. The older "three times a week" version remains in history; the current active fact becomes the Sunday routine.
Revision history keeps older wording visible when a habit changes—useful when you want to confirm what shifted and when.
Wellness should prefer the current revision in later turns. If an old fact looks stale, you might see Is this still accurate? under a reply. Until you answer, that entry is excluded from retrieval.
Stale wellness facts surface inline with Yes, still accurate, Edit, or Forget—not silently dropped from your profile.
Actions:
- Yes, still accurate
- Edit
- Forget
Closing the card without choosing means "review later," not rejection. The toolbar memory badge and Memory Center keep the queue visible.
What Wellness does not automatically get
Cross-agent memory is not a free-for-all.
Wellness should not receive unrelated Plan facts—for example literary interests meant for Learn or writing-style preferences meant for Write—unless domain rules and agent settings allow it. Custom agents only see domains you explicitly enable for them.
That boundary is why Personal Memory beats "copy the whole chat." You share facts, not threads.
For the product overview, read Personal Memory in AideAI: One Profile for Plan, Learn, Write, and Wellness. For privacy controls, read Local-First Personal Memory: Confirm, Control, and Delete What AI Remembers.
Where Agent Desk fits
If you keep Plan and Wellness open side by side during a heavy week, Meet Agent Desk: A Multi-Agent Workspace for Students keeps the workflows visually separate while Personal Memory carries the stable facts underneath.
Plan handles sequencing. Wellness handles humane routines. Memory keeps you from re-explaining the same baseline every time you switch panels.
A Thursday check-in you can copy
Plan thread
I train three times a week—Mon/Wed/Fri after class. Help me protect those slots around two midterms next week.
Wellness thread (later)
I'm exhausted tonight. What's a realistic movement option that doesn't wreck tomorrow's focus?
If memory is working, the second question should not require re-uploading your entire training history.
If something looks wrong
Open Settings → Application → Personal Memory → Open Memory Center.
Check:
- Active for current facts
- Needs review for unconfirmed proposals
- Needs update for stale entries
- History for revisions
- Access for which agent retrieved what (without query text)
Edit wording, confirm, forget, or export JSON from there. Full click-path detail lives in Personal Memory User Guide: How to Save, Review, and Control What AideAI Remembers.
Sustainable weeks need less re-explaining
Students burn time re-stating context that should be stable: sleep patterns, training cadence, explanation preferences, writing tone, schedule anchors.
Personal Memory is built for that boring but valuable layer—the facts you should not have to re-type every time you change agents.
For broader wellness framing, read How to Stay Productive in College Without Burning Out. For plan details, visit Pricing.
Download AideAI on Mac and try the Plan → Wellness pattern in two separate threads this week.