Skip to content
Docs section: How saving works

How saving works

Your agent can draft as much as it likes. StrongLog only changes when it saves a checked draft, and only when you ask.

Evaluate, then apply

Programmes and workouts are saved in two calls:

  1. Evaluate (stronglog_programme_evaluate or stronglog_workout_evaluate) checks the complete draft with the same validator the app uses. It returns any issues and a fingerprint of the exact content. Nothing is saved.
  2. Apply (stronglog_programme_apply or stronglog_workout_apply) checks again and saves everything in one step, or nothing at all. If the content changed since it was evaluated, the save is refused.

A good agent shows you the evaluated plan and waits for you to say “save”. Your instruction in the conversation is the approval.

No approval visit per workout

You grant permissions once, when you create the connection. After that you do not need to open StrongLog to approve each workout your agent saves. You can narrow or revoke the connection at any time.

Receipts

Every save returns a receipt. Your agent can list and reopen receipts later with stronglog_command_receipts, even in a different conversation, and read the saved result back with the matching read tool.

Changing something already saved

Updates name the revision they expect to replace. If the programme or workout changed in the meantime, for example from your phone, the update is refused instead of overwriting your change. The agent reads the current version and tries again with you.

Completed training is protected

  • Saving a plan never changes sessions you have already completed.
  • Corrections to logged sessions need a separate permission and keep a record of the change.
  • Deleting a planned session keeps your performed sets and the original receipt.

See the tool reference for every tool and what it does.