Repository navigation
Replies: 2 comments 2 replies
|
Hi @srothgan, Great proposal! We've already implemented a conversational "Chat-supported mode" in our soldsawn/openGym fork (https://github.com/soldsawn/openGym) that solves these issues:
We kept your core principle: Coach suggests, you decide. The main difference from upstream is our conversational flow while preserving the approval-based change system. Happy to share implementation details (300 lines across 4 files) or discuss how to bring this upstream via feature branch + PRs. Want to see the diff? 😊 |
|
Idea: an optional external memory provider for the Coach Self-hoster here, running the Coach against my own server — the rework in this thread solves the conversation and data-lookup side well. One gap stays open either way: the Coach can't remember what it's told between conversations. An injury, a piece of equipment I sold, "never program lunges," a schedule change — none of that becomes workout data, so a new conversation starts from zero on exactly what a real trainer would know. The embryo of this already exists: the profile's free-text fields (limitations / likes / dislikes / notes) are rendered into the Coach's context in Proposal: an optional memory provider, configured by the admin exactly like an AI provider, off by default:
Why the impact can stay small (from reading the code):
Fully understand if this is out of scope for the rework itself — planting it now because the tool surface is being designed in this thread, and that's the cheap moment to leave room for it. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What
Turn the Coach from a set of fixed actions into a conversation. You talk to it about your training the way you'd talk to a trainer: your workload, how a block is going, why your bench is stalling, whether to train tomorrow. It looks up whatever it needs from your data and answers you directly. When it thinks your plan should change, it suggests the change, and you still apply it with a button, exactly as today.
Why
The Coach looks like a chat, but every message gets turned into one of three fixed jobs: build a plan, review the plan, or debrief a workout. That causes a few problems:
How it would feel
What stays the same
Rough scope
This would be a full switch of the Coach to the new system, not a second mode next to the old one.
How to get there
If this is wanted, I'd suggest a dedicated feature branch. The work would be split into separate issues and PRs that merge into that branch, so main only gets the switch once it works end to end.
Questions
Related
All reactions