There is a problem with the automation system

Open 💬 2 comments Opened Jun 2, 2026 by vibo0917883709-blip
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

CODEX桌機板(WINDOWS)

What subscription do you have?

免費

What platform is your computer?

WINDOWS

What issue are you seeing?

Title:
Codex Desktop automation manual play creates empty session only

Environment:

  • Codex Desktop: 26.527.3686.0
  • CLI: 0.135.0-alpha.1
  • OS: Windows
  • Timezone: Asia/Taipei

Issue:
When I click the play button on an automation, Codex creates a new session/thread, but no message appears.

Observed:
The generated session JSONL contains only session_meta.
There is no user prompt, no assistant response, and no inbox item.

Example session:
C:\Users\User\.codex\sessions\2026\06\02\rollout-2026-06-02T09-58-04-019e860d-61e6-7823-bd23-cafb4c3f94db.jsonl

Expected:
Manual play should run the automation prompt and create a visible response or inbox item.

I tested with a minimal prompt:
"請立刻回覆一則測試訊息..."
It still created only an empty session.

What steps can reproduce the bug?

Title:
Codex Desktop automation manual play creates empty session only

Environment:

  • Codex Desktop: 26.527.3686.0
  • CLI: 0.135.0-alpha.1
  • OS: Windows
  • Timezone: Asia/Taipei

Issue:
When I click the play button on an automation, Codex creates a new session/thread, but no message appears.

Observed:
The generated session JSONL contains only session_meta.
There is no user prompt, no assistant response, and no inbox item.

Example session:
C:\Users\User\.codex\sessions\2026\06\02\rollout-2026-06-02T09-58-04-019e860d-61e6-7823-bd23-cafb4c3f94db.jsonl

Expected:
Manual play should run the automation prompt and create a visible response or inbox item.

I tested with a minimal prompt:
"請立刻回覆一則測試訊息..."
It still created only an empty session.

What is the expected behavior?

每天早上能夠在指定時間提供我一些訊息情報

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #24905

Powered by Codex Action

etraut-openai contributor · 2 months ago

English translation:

What version of the Codex App are you using (From “About Codex” dialog)?

Codex Desktop (WINDOWS)

What subscription do you have?

Free

What platform is your computer?

WINDOWS

What issue are you seeing?

Title:
Codex Desktop automation manual play creates empty session only

Environment:

  • Codex Desktop: 26.527.3686.0
  • CLI: 0.135.0-alpha.1
  • OS: Windows
  • Timezone: Asia/Taipei

Issue:
When I click the play button on an automation, Codex creates a new session/thread, but no message appears.

Observed:
The generated session JSONL contains only session_meta.
There is no user prompt, no assistant response, and no inbox item.

Example session:
C:\Users\User\.codex\sessions\2026\06\02\rollout-2026-06-02T09-58-04-019e860d-61e6-7823-bd23-cafb4c3f94db.jsonl

Expected:
Manual play should run the automation prompt and create a visible response or inbox item.

I tested with a minimal prompt:
"Please reply with a test message immediately..."
It still created only an empty session.

What steps can reproduce the bug?

Title:
Codex Desktop automation manual play creates empty session only

Environment:

  • Codex Desktop: 26.527.3686.0
  • CLI: 0.135.0-alpha.1
  • OS: Windows
  • Timezone: Asia/Taipei

Issue:
When I click the play button on an automation, Codex creates a new session/thread, but no message appears.

Observed:
The generated session JSONL contains only session_meta.
There is no user prompt, no assistant response, and no inbox item.

Example session:
C:\Users\User\.codex\sessions\2026\06\02\rollout-2026-06-02T09-58-04-019e860d-61e6-7823-bd23-cafb4c3f94db.jsonl

Expected:
Manual play should run the automation prompt and create a visible response or inbox item.

I tested with a minimal prompt:
"Please reply with a test message immediately..."
It still created only an empty session.

What is the expected behavior?

To receive some information at a specified time every morning

Additional information

_No response_

<!-- codex-issue-translator -->