Choose a useful name#
Use the project and the work being discussed, such as “Website docs — onboarding review.” Avoid titles so generic that several conversations look identical. A useful name helps you recognize the destination before replying.
Use the title-side editing action, review the new name and save it. If you cancel, retain the original name. Recheck the displayed title before using it as confirmation for a later message.
Keep naming separate from instructions#
If the work changes, state the new scope in the conversation. A renamed topic does not communicate requirements to the agent. Likewise, changing a title should not be used to imply that the agent completed a milestone.
The reviewed development record documents name validation, persistence and cancellation on a test conversation. It does not establish batch renaming, folder reorganization or a general remote task-management API. If a name does not update, report the app version and the visible state without resending unrelated task instructions.