Health & Symptom Tracker
Track food, sleep, and symptoms over weeks to find patterns — what triggers headaches, what worsens reflux, what helps energy.
Personal Lifeeasy~10m setup
- Tools
memorymemory_search- Channels
telegramios- Uses
cron
The "I think this thing makes me feel bad but I'm not sure" pattern is solvable with three weeks of casual logging. The trouble is that nobody keeps a paper journal long enough. Texting your bot when you eat or feel something off lowers the friction enough for the data to actually accumulate.
What it does
- Casual logging via chat — "had pasta at 8pm" or "headache, mild"
- Auto-categorises into food / sleep / symptoms / activity
- Weekly correlation report: "On the 4 days you ate dairy, you had headaches in 3." — pattern detection without statistical-significance promises
- Reminder cron — "haven't logged anything in 12 hours, remember to capture if anything's off"
- Privacy-first: data lives in your local memory, never leaves your server
What you'll need
- Memory for storage
- Cron for reminders + weekly summary
- Honesty about what you ate
Setup
1. Set the capture rules
Send to Flowly
Remember:
When I send something that looks like a food/symptom/activity log
(short, declarative, has a time or a what), categorise and store:
- "ate <X>" / "had <X>" → food
- "<symptom> <severity>" — headache mild, reflux 7/10 — symptoms
- "slept <hours>" / "bedtime <time>" / "woke <time>" → sleep
- "<activity> <duration>" — walked 40min, gym 1hr — activity
- "feeling <state>" — tired, foggy, energetic — wellbeing
Store with timestamp + category tag. Reply with just ✓ unless I'm
asking a question.
2. Reminder cron
Send to Flowly
Set up cron "health-checkin" three times daily — 11 AM, 3 PM, 9 PM:
If nothing has been logged in the last 5 hours, send:
> "Anything to log? — food, symptom, sleep, energy, mood."
Skip the reminder if I logged something in the last hour.
3. Weekly correlation report
Send to Flowly
Every Sunday at 7 PM, generate a report from this week's logs:
1. Counts by category — "this week you logged X foods, Y symptoms..."
2. Symptom heatmap — for each symptom logged, list the foods/sleep
patterns within 12 hours before
3. Pattern flags — when a symptom appeared 3+ times, surface the
most common preceding factor with this exact phrasing:
"Tentative pattern: <factor> preceded <symptom> in N of M cases.
This is suggestive, not proof — log a few more weeks."
4. NEVER make medical claims. Use words like "tentative", "suggestive",
"appears alongside" — never "causes" or "is caused by"
5. Send as Telegram message
Tips
- Three weeks before patterns emerge. A week of data is too noisy. Be patient before drawing conclusions.
- Keep entries short. "Pasta dinner, glass of wine" — not three sentences. Friction is the enemy.
- Don't trust correlations on small samples. The agent surfaces patterns; you decide whether to test them by elimination diet, earlier bedtime, etc.
- This is not medical advice. Patterns help conversations with your doctor. They don't replace them.
- Stop tracking when you have answers. Once you confirm dairy triggers your headaches, don't keep logging dairy forever. Tracking is for diagnosis; lifestyle changes are for after.