New task or follow-up: how to choose

Choose by whether the goal is continuing or changing. Keeping every request in one conversation can bury the constraints, while starting over for a small correction can discard useful context.

Compare the practical differences

Decision	New task	Follow-up
Best fit	A distinct objective or independent source packet	A revision to an existing deliverable
Useful property	Makes scope and outputs explicit again	Can use the saved task context and tool session
What to check	Requires restating all necessary context	Continuation depends on the tool and saved session

A concrete choice

Correcting a wrong date in summary.md fits a follow-up. Drafting an unrelated onboarding plan from different inputs is clearer as a new task.

Verify the choice

Name the output and source in either case. Review whether prior constraints should still apply before submitting the brief.

Write the reason for your choice into the task brief or setup notes. Then run a small representative task and compare the actual result with the requirement that drove the decision. Keep any unmet requirement visible rather than declaring the whole workflow ready from a single successful step.

Continue with the setup

The related desktop guide explains the relevant controls and limits. Use the current application state when applying this comparison; the presence of an option in a document does not mean every dependency on your computer is ready.