inspiration

a teammate forgot to take their medication, and that one moment cracked the whole thing open. medication apps everywhere, and most of them just yell at you on a schedule. they miss what's actually going wrong.

the real work is noticing. noticing the headache that always shows up after the morning pill. noticing you're going to run out on a wednesday. noticing the side effect that only happens on days you skip breakfast. that's the stuff a person who loves you would notice. we wanted to build that person.

we called it argus, after Argus Panoptes from Greek myth: the giant with a hundred eyes, the one who never closed all of them at once.

what it does

argus is an AI agent that watches over your meds so you don't have to.

  • log however you want. type it, talk to the agent, or just upload a photo of the pill bottle or the doctor's note. argus figures it out.
  • finds the patterns you'd miss. it lines your symptoms up against your medication timeline and pulls out the connections you're too close to see, like "your migraines are clustering on lisinopril mornings", and draws you the chart.
  • watches your supply. when a prescription is running low, argus drafts a refill email to your provider before you ever hit empty.
  • talk to it like a person. ask "how have my migraines trended this month?" or "draft a refill for my lisinopril" and you get back charts and drafts you can actually use.

how we built it

  • frontend: React 19, TypeScript, Vite 8, React Router 7
  • the brain: Google Gemini through @google/genai, wrapped in a tool-calling layer so the agent can actually do things: draft emails, pull correlations, render charts inline in the chat
  • charts: Recharts (symptom timelines, correlation plots, supply cards, daily schedule)
  • refill agent: its own little sub-agent with a separate prompt, schema, and tool set, just for writing emails to providers
  • workflow: scaffolded the UI fast with Claude Code, split features across Git branches, shipped to Vercel

challenges we ran into

picking the idea ate more of day one than we want to admit. and then (rookie move) we started building without feature branches, so when we finally tried to merge, half the files lit up with conflicts. untangling them hurt. but it forced us to adopt a real branching workflow halfway through, and the second half of the day was way smoother because of it.

accomplishments we're proud of

  • shipped a working, deployed agent in a single hack day after losing hours early on
  • a chat that renders real charts inline: the agent calls tools, gets data, draws the chart
  • a refill-drafting sub-agent that works end-to-end

what we learned

how to split work cleanly. how branches save you from yourself. how much further you can push a hackathon scope when the agent is actually doing the work. and for some of us, it was the first time driving Claude Code, a fast lesson in what it can do.

what's next for argus

  • real security for medical data: encryption at rest, proper auth, HIPAA-aware storage
  • one-click refills: send the drafted email after the user signs off, all the way through
  • wearable + pharmacy integrations so the data flows in automatically
  • on-device inference for the most sensitive correlations, so PHI never leaves your machine

Built With

Share this project:

Updates