Whether to create a new task with WorkBuddy depends not on the length of the conversation, but on whether the new requirements still rely on the original data, objectives, and intermediate results. If the same report continues to restructure, add data, or change formats, it should remain in the original conversation; If you change clients, projects, or start unrelated goals, the new task becomes clearer and reduces interference from old contexts.
In which situations is it appropriate to continue the original dialogue
- Continue editing newly generated documents, tables, or web pages.
- Supplement missing conditions, answer WorkBuddy's follow-up questions, or correct execution directions.
- Continue using the previously uploaded attachments, work catalog, and previously confirmed specifications.
- Open completed, failed, or interrupted tasks and request continuation from existing progress.
The original task preserves the previous context. When following up, you don't need to restate the full background, but you should specify the specific target. For example, don't just say "optimize further," but rather "compress the second part of the report into three paragraphs and keep the data table."
In which situations is it best to create a new task?
| Situation | The reason |
|---|---|
| The client or project has changed | Avoid cross-linking characters, data, and calibers |
| The objective is unrelated to the original mission | Reduces invalid contexts, facilitating independent acceptance |
| Different work directories are required | Make document read-write boundaries clearer |
| I want to handle another matter at the same time | New tasks can run independently and manage their status |
When creating a new task, first select the correct workspace, then add context by uploading files, screenshots, or citing materials. Don't cram multiple irrelevant items into the same session just to "make it remember more," and don't assume WorkBuddy automatically knows what another task just did in a new task.
How do you recover them after having too many tasks?
The task list can be filtered by status and date, or you can search historical tasks. When naming, clearly state the project, deliverables, and date, making it easier to search than "new task" or "continue modifying." If you encounter failure or interruption, open the original task and look at the final step: if the goal remains unchanged, continue the conversation directly; If you plan to overturn the plan or switch the data scope, create a new task and reference the confirmed input.
A simple way to judge: the new instruction must rely on the old result to be clear, so continue; Even if the old dialogue is deleted, it can be described independently and created as new. This not only preserves necessary context but also reduces the risk of misusing files and requirements across projects.
