openai / openai/codex

[Windows] Scheduled automation tasks are missing from Pet activity tray in Running and Ready states

Open
#39,412 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app automations bug pets windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using?

26.814.5167.0 (Microsoft Store/AppX)

What platform is your computer?

Windows 11; ARM64 app package

What issue are you seeing?

Standalone scheduled automation tasks run and complete successfully, but never appear in the floating Pet activity tray while Running or after completion as Ready. Normal manually started tasks appear in the tray at the same time.

This was reproduced with a custom v2 pet. The pet itself is awake and the overlay is visible, so the evidence points to activity-tray filtering/state presentation rather than the pet sprite package.

What steps can reproduce the bug?
  1. Open Codex Desktop and wake the pet.
  2. Start or keep a normal manual task open and confirm that it appears in the Pet activity tray.
  3. Create a standalone local scheduled automation that runs for about 60 seconds and produces a non-empty final response/inbox item.
  4. Watch the Pet activity tray during the full run.
  5. After the automation completes, check the tray again without opening the completed task.
Expected behavior

The scheduled task should appear in the Pet activity tray as Running during execution, then as Ready while its completed result remains unread.

Actual behavior

Only the manual task is shown. The scheduled automation is absent from the visible tray both while running and after completion.

A controlled reproduction ran for approximately 74 seconds. During that run:

  • the scheduled thread was reported as active and later completed with no error;
  • events were routed to avatarOverlay while the overlay renderer was visible;
  • status/reasoning updates reached both the primary window and avatarOverlay;
  • avatarOverlay created one inbox item at completion;
  • the completed thread was added to the local unread-thread state;
  • nevertheless, the task never appeared visually in the Pet activity tray as Running or Ready.

Sanitized reproduction reference:

  • Test thread: 01a01838-b82e-7e83-939a-d77c1ff63d67
  • Overlay route: 2026-08-19 12:12:45 Asia/Taipei
  • Active run: 12:12:47–12:14:01
  • Avatar-overlay inbox item: 12:14:01
  • Unread-state update: 12:14:02
Additional information
  • A full app exit/restart and update to 26.814.5167.0 did not fix the issue.
  • The same behavior reproduced twice with temporary test automations.
  • The temporary automations were removed after testing.
  • No supported setting or per-task mute/hidden state was found.
  • No private logs or local paths are attached.
  • Read-only bundle inspection suggests automation-sourced threads receive special notification-tray filtering. This is an inference, but it is consistent with automation tasks being hidden despite valid overlay routing, inbox creation, and unread state.

Related, but not identical:

  • #24302 — pet tray omits active local threads
  • #32994 — Windows pet task-tracking behavior
  • #28995 — pet overlay state/animation mismatch

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by tracing how scheduled automation events reach avatarOverlay, how the activity tray filters threads, and how the unread-thread state becomes a visible Running or Ready item. Done means a standalone scheduled task appears during execution and remains visible as Ready after completion, without opening the task.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.