29 lines
997 B
Markdown
29 lines
997 B
Markdown
---
|
|
name: thread-naming
|
|
description: Use when a Codex agent should keep the current thread title short, rename a thread after the user asks for it, or update the title when the task goal becomes clear.
|
|
---
|
|
|
|
# Thread Naming
|
|
|
|
Keep thread titles short and useful for later resume lists.
|
|
|
|
## Rules
|
|
|
|
- Use 3 to 6 words when possible.
|
|
- Prefer concrete nouns and verbs from the current task.
|
|
- Do not include dates, user names, punctuation-heavy labels, or generic words like "chat" unless needed.
|
|
- Rename once the task goal is clear, and again only if the goal materially changes.
|
|
|
|
## How to Rename
|
|
|
|
- If the client exposes a thread rename or `thread/name/set` capability, use it with the concise title.
|
|
- If only Telegram commands are available, tell the user the exact `/rename TITLE` command to run.
|
|
- If no rename mechanism is available, include a short suggested title in the final answer.
|
|
|
|
## Examples
|
|
|
|
- `Fix Resume Buttons`
|
|
- `Publish Gitea Repo`
|
|
- `Format Tool Output`
|
|
- `Add Rename Command`
|