328 karma · joined February 26, 2010
It's a cli that runs a server, a browser-based UI (where the audio happens), and a set of scripts to install hooks for various harnesses.
That said, I’ve switched one vault to git and have had no issues there.
Dead Prez - Hell yeah: https://youtu.be/kGjSq4HqP9Y?si=_z6jb0Vfo7_PiITQ&t=82
Maxo Kream - 5200: https://www.youtube.com/watch?v=7kC9j6Zp-kg
Maxo was actually arrested for racketeering, though not due to this song specifically (I don't think).
https://phys.org/news/2018-02-power-grid-fluctuations-hidden...
All that said, I’ll try to add some examples to the readme.
I love the use of a notebook as an updating dashboard here. One of my demos before this MCP server was an evidence.dev dashboard.
I think supporting the native Apple Health export feature would be a good idea. It just takes longer than the CSV export, so I started there. I would imagine the native export has more data, though, which might be nice.
My general belief around data agents is to offload as much as possible to SQL.
I haven't experimented with MCP too much because I have some reservations about it, but I decided to go MCP-first for this to see how it feels to prototype around it. My typical flow would have been to go sqlite+sveltekit.
But I'd like to revisit it because it would be a natural fit to just put the personal trainer flow directly in an app.
I would like to go back to this though and add it as an integration option.
Or if you want to work more manually, you could do the same but not allow full access to git commit. That way it will request access each time it’s ready to commit and you can take that time to review diffs.
Here’s the LM Studio docs on it: https://lmstudio.ai/docs/app/advanced/speculative-decoding