skills.rest
ma08
ma08COMMUNITY
Explore all skills by this author →
Website𝕏@curious_queueGitHub

rename-codex-thread

Rename Codex thread labels in the SQLite state database with timestamped backups.

28|Updated Jan 3, 2026
Search Tags:#automation#codex#sqlite#session-management#task-tracking#coding-agents#thread-renaming
One-click install
npx skills add https://github.com/ma08/botfiles --skill rename-codex-thread
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rename-codex-thread
Source: https://github.com/ma08/botfiles/tree/main/codex/skills/rename-codex-thread
Command: npx skills add https://github.com/ma08/botfiles --skill rename-codex-thread

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Codex app threads default to displaying the first user prompt as their label, making it difficult to locate specific threads in the sidebar when running multiple long-lived coding agent sessions. This Skill solves that by enabling quick, consistent renaming of thread labels to clear, trackable titles.

Core Features & Use Cases

  • Local State Renaming: Updates thread titles and previews directly in the authoritative Codex SQLite state database, rather than only modifying the optional session index file.
  • Consistent Labeling Convention: Supports a default title format that includes tracker identifiers (such as Linear ticket IDs or GitHub issue references) for seamless alignment with existing task tracking workflows.
  • Safety Guardrails: Automatically creates timestamped SQLite backups before making any writes, and supports dry-run mode to preview changes before applying them.
  • Use Case: If you have a thread labeled with the initial prompt $start-new-task ZON-218, you can rename it to ZON-218: Research Stanford Autonomous Agents Lab collaboration path to find it instantly in your Codex app sidebar later.

Quick Start

Ask your AI agent to rename your current Codex thread to a clear, trackable title using the rename-codex-thread skill.

Frequently Asked Questions about rename-codex-thread

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rename Codex threads for easier identification in the sidebar?▼

To rename Codex threads, you can use a skill that modifies the authoritative Codex SQLite state database and updates the session index JSONL file, replacing default prompt labels with clear titles. It creates timestamped backups before writing any changes.

Why does my Codex app show the initial prompt as the thread title instead of a readable name?▼

Codex app threads default to displaying the first user prompt as their label, making multiple long-lived coding agent sessions hard to locate. Renaming them to trackable titles with tracker IDs resolves this sidebar clutter.

Can I preview thread label changes in Codex before applying them to the SQLite database?▼

Yes, you can preview thread label changes using the dry-run mode. This safety guardrail shows what modifications will occur before any writes are made to the authoritative Codex SQLite state database.

Does renaming a Codex thread update the local SQLite state database or just the session index file?▼

Renaming a Codex thread updates the authoritative local SQLite state database directly, rather than only modifying the optional session index JSONL file, ensuring consistent thread metadata across your local state management workflow.

How do I format Codex thread titles to include Linear ticket IDs or GitHub issue references?▼

You can format Codex thread titles using a default convention that includes tracker identifiers like Linear ticket IDs or GitHub issue references, creating clear and trackable names for seamless alignment with task tracking workflows.

What's the best way to organize long-lived coding agent sessions in the Codex app?▼

The best way to organize long-lived coding agent sessions is by renaming thread labels to clear, human-readable titles with tracker IDs. This modifies the Codex SQLite database and maintains consistent metadata for fast sidebar identification.

Related Skills

Explore More Software Engineering Skills→
filipexyzfilipexyz
6

sessions

Manage persistent AI agent sessions and inspect SQLite traces in Ravi.

Community
Advanced
ma08ma08
28

start-new-task

Create structured task folders with session, machine, and tracker metadata.

Community
Advanced
ma08ma08
28

create-ticket-session

Create Linear tickets and launch detached zellij/Codex worker sessions.

Community
Intermediate
ClawStackStudiosClawStackStudios

Scuttle-Skill: scuttle-db-backup

Copy SQLite database files into timestamped backup directories.

Community
Basic