Continuing goals

A continuing goal belongs to a Thread branch and continues its latest run. Sending an ordinary message does not create a goal.

1. Send a message to create work.
2. In Continuing goals, choose Create goal.
3. Enter a self-contained objective and an optional output-token budget, then choose Start goal.

Only one unfinished goal can exist on the branch. The latest run may already have finished. An ordinary final answer ends that run; the agent can explicitly report the goal complete or blocked with goal_report. The panel shows the authoritative status and blocker.

Use Edit, Pause, Resume, Complete or Cancel goal as appropriate. These controls change future authorization. Already dispatched calls and independent processes still settle. Stop run also pauses its goal; a separate policy pause still needs its own resume. Complete or cancelled goals require a new goal to authorize more work.

The budget counts provider-reported output before further dispatch. Blank means no configured limit; zero allows no further output dispatch. In-flight work can exceed the budget. Estimated and missing usage are shown separately; incomplete completed usage blocks further inference while a budget is set. Do not add input, cache and reasoning fields into a total, because provider counts can overlap.

The Application Host must remain running. See Scheduled tasks and follow-ups for timed work.