Nexus

Correct one existing workout, meal, or body-weight record using its type, id, and state_version returned by Nexus history or logging. Send only the fields the user wants corrected; omitted fields stay unchanged, and workout exercise identity cannot change. If the state version is stale, read the latest record and retry the correction with a new request id.

nexus_update_entry

Read the user's Nexus records to answer questions about workouts, meals, nutrition totals, body weight, goals, progress, comparisons, or personal records. Use this before analysis, coaching, or recommendations that depend on the user's actual history. Request one date or a date range, and narrow by entry type, muscle category, or friend when relevant. Use nexus_show_interface instead when the user wants to see or edit a Nexus day.

nexus_get_history

Log completed workouts, consumed meals or drinks, or body weight immediately. When this returns status: "logged", call nexus_show_interface so the user can see what was logged and edit it if needed. Estimate meal calories, macros, and dietary fiber before calling; Nexus stores the values you provide. Send every record from the user's request in one batch. The batch is atomic: if any exercise does not match an existing definition, nothing is written and the result returns candidates; retry the complete original batch using a returned exercise_id only when the movement, equipment, and angle match, or use create_exercise=true only when none of the returned exercises matches. Do not use for workout planning, general nutrition questions, or history analysis.

nexus_log_entries

List the user's Nexus friends, pending requests, and friend code, or add, accept, reject, or remove a friendship. Add a friend with their NEXUS-XXXX code; accept, reject, or remove by email. To read a friend's shared fitness history, call nexus_get_history with the returned friend_id.

nexus_manage_friends

Use this to create a workout plan whenever the user asks what workout to do, requests a workout recommendation, wants to train a muscle today, or has chosen a workout to start. Choose the exercises using Nexus history or goals when useful, then create the plan in the same response; do not only describe it in chat or ask for separate confirmation. Nothing is logged until the user records completed sets and taps Finish. Use exercise_id from Nexus when available, and always include the closest muscle category. For a workout already completed, use nexus_log_entries instead.

nexus_prepare_workout

Change the user's daily calorie, protein, carbohydrate, fat, or dietary fiber target only when they explicitly ask. Send only the targets being changed; omitted targets keep their current values. Include the user's reason when they provide one. Nexus keeps past goals so earlier records retain the target that applied then.

nexus_set_goal

Open a Nexus day so the user can see and edit workouts, meals, nutrition totals, goals, personal records, and body weight. Call this after every successful nexus_log_entries result and whenever the user asks to open or see Nexus. Use nexus_get_history instead when you need data for analysis or coaching.

nexus_show_interface