20 May 2026
I have been using Hermes to track my powerlifting workouts, and the setup is intentionally simple.
There is no fitness API in the middle. No separate database. No dashboard I have to remember to open after training. The agent stores each workout as structured text in this GitHub repository, right next to the rest of the site.
That sounds almost too plain, but it is the part I like. A workout is just data: date, focus, sets, reps, weights, RPE, notes, and accessories. The agent can turn a messy phone conversation from the gym into that structure, then update the site from it.
The useful piece is the skill around the data. Hermes knows how I want workouts recorded. It follows the live exercise order, prompts me for the next set, handles changes when equipment is taken, and asks for final notes when the session is done. If I say I am moving from squats to curls because the benches are full, it keeps up.
Afterward, the record lives in Git. That gives me history, diffs, and a site update from the same workflow I already use for writing and code. The data is portable because it is just text. The presentation can change later without losing the log.
I like this pattern because it makes the agent feel less like an app and more like a thin layer over my own files. The workout happens in the gym. The record lands in the repository. The blog and powerlifting page render from there.
For now, that is enough. I want the habit to be easy to keep, and this makes logging a session feel closer to sending a text than filling out software.