Baymax
Baymax · Built on Hermes Agent

A chief of staff, not another chatbot.

Baymax notices what changed, prepares what matters, and follows through, so your household spends less time coordinating and more time living.

01 / Outcomes

Product in Action

Baymax notices what changed, prepares what matters, and follows through while staying quiet when nothing needs your attention.

01 / DAILY ORCHESTRATION

Your morning, already sorted.

Every morning, Baymax combines the shared calendar with staged triage across three Gmail inboxes. Exact rules remove cancellations and stale signals; bounded classification filters the rest. The briefing shows what changed, what is already handled, and the one decision most worth making.

Integrations
31 Google Calendar
Gmail
Telegram
Baymax
bot
Today
⚡ Daily Brew

I found 14 changes. Thirteen are handled or non-actionable.

Only one decision needs you; the options are ready.

✉️ What changed:
• The insurer replied; I updated the claim draft.
• Thursday’s pediatrician appointment is confirmed for 11:00 AM.

✓ Already handled:
• Birth registration is complete.
• 12 low-priority messages were filtered out.

Your one decision: A calendar overlap at 11:00 AM. Reply options to compare two prepared fixes.

7:45 AM
02 / FUTURE PLANNING

It sees around corners.

Once a week, Horizon looks 12 weeks ahead across household commitments, the shared calendar, and relevant messages. It surfaces at most three blind spots while there is still time to act, then waits for a simple add or skip.

Integrations
31 Google Calendar
Gmail
Telegram
Deep Research
Baymax
bot
Sunday
🔭 Weekly Horizon Scan

I looked 12 weeks ahead. One item is worth planning now.

October family trip
Travel documents are not on the plan.

Why now:
A passport check this week leaves time for a normal renewal if needed.

Suggested next step:
Add “Check passport expiry” for this week.

Reply add or skip. Nothing changes until you approve.

3:00 PM
03 / FAMILY HEALTH

Health context, carefully bounded.

Baymax combines freshness-aware signals from Huckleberry, Fitbit / Google Health, and an owner-private Oura adapter. Missing streams stay missing instead of reading as zero. Tentative household correlations are labeled as observations, never causes.

Integrations
Huckleberry
Google Health
Fitbit
Oura Ring
Baymax
bot
July 13
🏃 Body Coach Briefing

Recovery call: You slept 6.8 hours, your best night since the baby arrived. Readiness is still 38 and HRV is down, so one better night has not erased the week’s accumulated sleep debt.

Plan adapted: No barbell today. Baymax has replaced the programmed session with one 20-minute stroller walk and optional floor mobility.

Data boundary: Nutrition is not being tracked, so I am not scoring it or inventing a trend.

Your one action: Take the stroller walk whenever the window opens. The rest of the plan can wait.

7:46 AM
PJ
PJ + Baymax
3 members
Today
👶 Baby Trend Update

Baseline ready: 79 sleep cycles, 131 feeds, and 78 diaper records now give Baymax enough coverage to watch for repeatable patterns.

Signal, not advice: Sleep cycles following recorded bottle feeds were longer on average, but this is observational, intertwined with feeding patterns and the baby's changing baseline, and not a reason to alter feeding.

Parent sleep may move with the baby's total sleep, but only seven overlapping nights are available and the relationship is not statistically reliable.

Decision: Keep care unchanged and logging consistent. Baymax will surface this again only if the pattern repeats with more evidence.

12:05 PM
04 / HOUSEHOLD MEMORY & AUTOMATION

Context that closes the loop.

Baymax keeps canonical household commitments separate from conversational memory. It gathers the relevant context, prepares the next step, and waits at the boundary where approval matters. Optional Obsidian-style views are generated from that state, never treated as the source of truth.

Integrations
Gmail
Telegram
Obsidian
Allianz
PJ
PJ + Baymax
3 members
Today

What is the status of birth registration and the insurance claim?

1:29 PM
⚡ Household Status

✓ Canonical state: Birth registration is marked [x] complete.

📄 Insurance claim:
• Draft prepared from the attached receipt.
• Required fields checked.
Nothing has been submitted.

One action: Reply review to inspect the claim draft.

1:30 PM
Built for a household, not a user

The right message. The right person. The right moment.

A household chief of staff needs more than shared context. Baymax understands who should know what. Shared logistics go to the family conversation, personal matters stay private, and nothing is sent when there is nothing useful to add.

PJ + Baymax · shared household
Thursday changed Pediatrician · 11:00
Coordination Both calendars checked ✓
Private follow-up Claim draft sent to Pat
One shared update Both need to know

Shared when the household needs to move together

Appointments, travel, and family decisions go to the shared thread. Personal details and private follow-ups stay out of it.

Baymax
Knows the audience for every update
Family logistics Appointments, travel, shared deadlines.
PJ group
Body, finance, and admin Personal details and coaching.
Pat only
Recovery and baby context Personal guidance and check-ins.
Jenny only

Private when it belongs to one person

Baymax can support two people without turning the household chat into a data dump. Each update goes only to the person who should see it.

Nothing needs you
Inboxes, calendar, and commitments checked
Quiet by design
3 sources checked
0 changes needing action
0 messages sent
Everything is on track Next scheduled check tomorrow at 9:30.
No action

Silent when there is nothing worth saying

A useful chief of staff protects your attention. Baymax skips empty updates, avoids repeated reminders, and speaks only when something has changed.

02 / Automated Orchestration

Observe. Verify. Decide. Act. Reconcile.

Baymax prepares bounded evidence, verifies exact facts with code, applies model judgment only where ambiguity remains, and records approved outcomes back into canonical state.

01 / Observe

It monitors changes silently. A cancelled meeting, an email deadline, or baby sleep logs, all captured and prepared.

Gmail ×3 Shared Calendar Huckleberry Fitbit Milestones

02 / Verify

It validates the facts. Code instantly structures the agenda, filters cancellation rules, and checks overall system health.

Inbox Triage Cancellations Filter Freshness Check Project State

03 / Decide

It structures bounded options. Horizon can propose up to three useful next steps, while low-value output is suppressed.

Routing Logic Noise Filters Daily Brew Body Coach Baby Scout

04 / Act

You stay in control. Allowlisted deterministic loops act inside their safety policy; consequential external actions stop for approval in Telegram.

Safety Allowlist Telegram Approval Gate

05 / Reconcile

It applies unambiguous replies once, deduplicates handled messages, and updates canonical household commitments.

Reply Reconciler Deduplication Canonical JSON
freshness, privacy routing, safety policy, approval boundaries

Platform System Map

Less to remember. Less to chase.
More handled.

Hermes made the agent possible. Baymax made it dependable: deterministic where truth matters, agentic where judgment helps, approval-gated where consequences matter, and quiet when the family needs less technology, not more.