codex - 💡(How to fix) Fix Feature request: automation/session title templates with date/time variables [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#22475Fetched 2026-05-14 03:35:19
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Root Cause

  • Makes recurring automation runs much easier to scan and distinguish
  • Reduces the need to manually rename each session
  • Avoids awkward prompt hacks like asking the model to rename the conversation every run
  • Fits common automation/reporting workflows (daily/weekly digests, monitoring, reminders)
RAW_BUFFERClick to expand / collapse

What feature would you like?

Please add support for dynamic title templates for Codex automations and/or the sessions they create.

Today the automation name/title appears to be a fixed string. That makes recurring automations hard to distinguish in the session list unless the model manually includes the date in its response.

Example use case

I have a daily GitHub-trending automation. I want each run to create or rename the session title automatically to something like:

  • 2026-05-13 GitHub每日热点
  • GitHub Daily Hotspots - 2026-05-13
  • Weekly Review - 2026-W20

Requested behavior

Support variables/placeholders in automation titles (and ideally session titles), for example:

  • {date}
  • {time}
  • {datetime}
  • {yyyy-MM-dd}
  • strftime-like formatting

It would also be great if the same templating could be used when naming the thread/session created by an automation run.

Why this matters

  • Makes recurring automation runs much easier to scan and distinguish
  • Reduces the need to manually rename each session
  • Avoids awkward prompt hacks like asking the model to rename the conversation every run
  • Fits common automation/reporting workflows (daily/weekly digests, monitoring, reminders)

Related issues

This seems adjacent to, but not the same as:

  • #15533 Add ability to rename Codex chat/session titles (CLI + VS Code)
  • #5019 Dynamic Expressions, Command Substitution, and Context Variables in Custom Prompts

This request is specifically about first-class dynamic naming for scheduled automation runs.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Feature request: automation/session title templates with date/time variables [1 participants]