autogoal
Autogoal
Use native goal tools when the user explicitly requests a goal, directly or through a standing instruction that covers the current request. Apply that instruction without asking again or requiring a separate skill invocation. Without such a request, an ordinary task, plan, audit, or measurable outcome does not itself authorize create_goal.
Standing requests
The project or current conversation may record the user's request to use Autogoal for long-running work by default. Honor its exact scope. Long-running work means a substantial objective with multiple execution, investigation or verification checkpoints and an acceptance ledger, such as a large audit, multi-gap implementation, migration, or sustained investigation. It does not mean every question, small edit, slow command, or task with a time limit. No invented minute or token threshold is needed.
When that standing request applies, start or reuse the goal before extended work. If initially small work grows into that scope, apply the request then. A direct opt-out such as “no goal” wins. Keep read-only, plan-only, human-assignment and publication boundaries unchanged; the goal's completion threshold ends at the actual requested outcome. Explaining or editing a skill is not invoking that skill, though the work may independently meet the standing request.
Pause and resume
On a direct “pause”, “stop”, or “hold”, immediately mark the existing plan Status: Paused, record the user's instruction, preserve open obligations and the saved next step, and make the current next action wait for explicit user resumption. Do this before a requested detour such as skill or task-history repair. A spoken acknowledgment or private note does not pause the plan.
Use a supported native pause control only when its current contract allows it, and verify the result. If none is available, record that limitation in the same plan and tell the user once; do not claim the native goal is paused, fake completion/blockage, or alter internal goal storage. End the turn promptly. Never create sleep/poll loops, repeated reminders, or another goal to manage a pause.
On automatic continuation or recovery, check the plan's pause state before selecting work. Scheduler-generated continuation is not a direct user resume. Keep paused work stopped; an explicitly requested repair may proceed within its own scope. Resume only on a direct user instruction, then update the existing plan and revalidate its saved next step. See pause handling.