Health tracking without the limitations of AI chatbots
AI chatbots have limitations around memory, numbers and types of attachments, connectors, storage, and other resources. The underlying LLMs also change over time, and data leakage is a concern. Code-based versions such as Claude Code and Grok Build can store essentially unlimited files on your computer, organize them with databases and files, connect to public and private MCPs, and even host interfaces for reviewing results. You can choose between a hosted LLM such as Claude, Grok, or ChatGPT and a local LLM if you prefer. The best part is that these code-based versions have no memory between sessions: everything is stored on your computer, assuming a basic subscription. You start by prompting the system about the domain, what you want to store, how you want to access it, and other requirements. Then it creates the system for you. I started with my own personal health archive. I'm comfortable using the terminal interface for Claude Code and Grok Build, so I use that directly. When I built one for my wife, she couldn't use the terminal, so I had it build a basic website with Q&A interfaces, data access, and upload functionality. I hosted it on my Mac, and I wrote no code. We loaded hundreds of documents in various formats into each of our instances without any trouble. When we have new files, we can simply drop them in. For specific questions or health events we're tracking, the system has perfect memory and no memory limits within the archive. For my archive, I use a Garmin watch and a food tracker. Because public MCPs weren't available for those services, I had the system build local MCP servers by reverse-engineering them. My health tracker now has a continual feed of my food, fitness, sleep, and other data. My wife has some chronic health issues, and we had reached a point where the standard chatbots were hitting their limits. We were struggling and didn't know what to do, so I discussed it with Claude, and we came up with this approach. The best part, besides getting a better handle on our health, is that I can launch any LLM within the project—Claude, Grok, or others—and use it for that session. The project isn't tied to or limited to a single LLM. That lets me manage costs, switch to better LLMs as they improve, and use specialized models for deep research, all while working with one data set. 1. I prompted a code-based AI about the health domain, the information I wanted to store, and how I wanted to access it. 2. I created a personal health archive and loaded hundreds of documents in various formats into it. 3. I built a second archive for my wife with a basic website, Q&A interfaces, data access, and upload functionality, then hosted it on my Mac. 4. I added new files by dropping them into the appropriate archive. 5. I had the system build local MCP servers for my Garmin watch and food tracker by reverse-engineering those services when public MCPs weren't available. 6. I used the resulting health tracker to maintain a continual feed of food, fitness, sleep, and other health data. 7. I launched different hosted or local LLMs within the same project as needed for each session, including using specialized models for deep research.
0 comments