Skip to content

End a program when the block is done

1 min read1toolUpdated Sep 28, 2026

— Say it like this
That's the program done — wrap it up.
2 more ways to say it
  • End the current program.
  • Close out this block. I'm switching to a new program Monday.
— Here's how it goes

What you'd see in chat

  1. That's the program done — wrap it up.
  2. The program is complete. Its own routine and diet executions have ended together, while past sessions and meal logs remain available. Your plan definitions are still saved for reference. If the response lists a linked plan under nextActions, that execution was started independently or before ownership was recorded; I'll ask what you want to do with it separately.

The current training block is finished, and you want to close its execution before starting another.

What happens when you complete a program

complete_program completes the program and ends its open execution. An active routine or diet execution created by that exact program execution closes in the same transaction. The routine and diet plan definitions remain saved, and past sessions and meal logs remain readable.

A linked plan may have been started independently or before the system recorded execution ownership. The program will not close that execution based only on a matching plan ID. The tool response lists such a plan in nextActions; ask the athlete whether to keep it active, pause it, or complete it before making another change.

Pausing a program pauses its own routine execution and ends its own diet execution. Resuming the program starts a new diet execution only when that program pause ended the previous one. A diet the athlete paused separately stays paused. Deleting the program ends its owned executions and keeps the plan definitions.

The command accepts the program ID. It does not accept a closing note, a backdated completion date, or a frozen summary. For adherence, training progress, or body changes, use the relevant progress tools and identify their actual time range. Do not describe their answer as an immutable snapshot created by program completion.

Agent sequence

  1. Identify the program and confirm the athlete wants to complete it.
  2. Call complete_program once, using a stable request ID for retries.
  3. Report only the status and child outcomes returned by the call. If nextActions contains plans, present those choices and wait for an explicit answer before changing them.
  4. Read the program and linked plans back when the caller needs to verify their final state. If a write response is lost, read the current state before retrying.
— Related