Agent skill · ma08
rename-active-codex-threads
Rename all recently active Codex threads across the local app and connected remote hosts with native codex_app thread tools, using tracker ID, stable task domain, and current status. Use when the user asks to update, refresh, normalize, or rename active/recent Codex thread names in one batch, or invokes $rename-active-codex-threads.
What it needs
About 6k tokens when loaded.
What this skill does
Rename Active Codex Threads Run the shared thread-naming workflow immediately rather than waiting for the recurring automation. Safety Contract This is a user-visible batch change. Use a two-phase workflow: 1. Build and validate the readable inventory returned for currently available local and connected-remote hosts. 2. Attempt every eligible candidate independently and collect decisions for every successful, confident read. 3. After all candidates have been attempted, call native codexapp.setthreadtitle for confirmed changes and skip failed or uncertain candidates. If listthreads itself is incomplete, unreadable, or times out, make no title changes anywhere in that run. Otherwise process every host returned as available. A failed or unreadable candidate affects only that thread: skip it, continue with the remaining candidates, and report the failure. Skip offline, unavailable, retired, or unlisted hosts; do not require hardcoded or historically seen hostnames. Do not use a local SQLite/database fallback for a batch run. Naming Contract Use this naming convention: Use a human-facing Linear ID or GitHub issue reference; never use raw tracker UUIDs. Use [no ticker] when no tracker exists. Treat a leading run of ASCII hyphens before the tracker as a user-managed visual-divider prefix. Strip it only while parsing and comparing the three-part base title, then reattach the exact captured prefix on every rename. Never shorten, lengthen, remove, or relocate an existing generic prefix. For a confidently identified orchestrator, umbrella, parent, bucket, index, or group-overview thread that has no existing prefix, add the default prefix ------ only when no other thread in the same confirmed group already has a visual-divider prefix. This divider addition is allowed even when the base title has no material status change. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ma08/rename-active-codex-threads--529161