---
title: "Rename a topic so it is easier to choose"
description: "CueSpec’s Mac task details include a topic-name editing action."
slug: "rename-task"
category: "agent-management"
language: en
editorial_status: published
capability_status: available
reviewed_at: 2026-10-13
keywords: ["CueSpec rename task","Codex conversation title","task naming"]
---

# Rename a topic so it is easier to choose

CueSpec’s Mac task details include a topic-name editing action. Renaming changes conversation metadata; it does not send a new prompt or change the task’s actual objective.

## 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.

## Related reading

- [Check several projects without mixing their instructions](/parallel-project-check-in/)
- [The original conversation is unavailable for sending](/conversation-owner-unavailable/)
- [A task is missing from the list](/task-not-visible/)
- [CueSpec product facts at a glance](/product-facts/)
