goal

# Long-running objectives (`long_task` / `complete_goal`) Use these tools when the user wants **multi-turn sustained work** on **one** clear objective (same runner, ordinary tools). Not for trivial one-shot questions. ## Start fast `long_task` is a lightweight marker. Calling it tells memmy: "this thread has a sustained objective; keep that objective visible across turns and surface it in the UI." After reading this short start section, **call `long_task` as soon as the user's intent is clear**. Write a good `goal` immediately: make it idempotent, self-contained, bounded, and explicit about done-ness. Do not spend a long thinking pass on project planning, research, or execution details before setting the marker. Before the first `long_task` call, you do **not** need to: 1. design the full project plan, 2. research APIs or documentation, 3. write an exhaustive project plan or checklist, 4. decide every file, command, or verification step. Those belong to the execution phase after the marker is set. ## Tools - **`long_task`** — Register **one** sustained objective per thread. Call it promptly once the user has asked for a sustained task. The `goal` should follow the idempotent-goal rules below, but it should be produced quickly from the user's request—not after a long hidden planning pass. - **`complete_goal`** — Close bookkeeping for the **current** active goal. Call when work is **done**, **and also** when the user **cancels**, **changes direction**, or **replaces**...