Scheduled → Create silently creates a normal thread when an SSH remote project is selected

Codex App version

Not captured from the About Codex dialog at the time of reproduction. It can be provided privately if required.

Subscription

Not included in this public report.

Platform

Codex Desktop on macOS, connected to a Linux project through the built-in SSH remote-host workflow.

What issue are you seeing?

Starting from Scheduled → Create, Codex Desktop allows an SSH-connected remote project to be selected. The creation conversation opens with the expected remote project, remote connection, and SSH host visibly selected.

However, after asking Codex to create a recurring scheduled task, the flow silently produces a normal remote Codex thread instead of registering an automation:

• no Automation ID is generated;
• no corresponding task appears in the Scheduled list;
• the resulting thread is recorded as a normal Codex thread;
• the automation create/update capability is not exposed to that thread;
• no unsupported-target error or other failure message is shown.

The remote environment itself works correctly in the resulting thread. It can access the selected remote working directory, project files, a project-specific skill, the remote shell, and a connected email tool. The failure is specifically at the automation control-plane registration step.

This is particularly misleading because the user entered through the Scheduled creation UI and the resulting conversation continues to display the selected remote target.

Steps to reproduce

1. Open Scheduled in Codex Desktop.
2. Click Create.
3. Select an SSH-connected remote project and its remote working directory.
4. In the generated creation conversation, request a recurring scheduled task.
5. Allow the conversation to finish.
6. Inspect the Scheduled list and the resulting thread.

Actual behavior

The resulting item is a normal remote Codex thread. No scheduled automation is registered, and the UI does not report that the selected execution target is unsupported.

Expected behavior

Codex Desktop should do one of the following:

1. register a native Scheduled task targeting the selected SSH host and project; or
2. reject or disable that target before opening the creation conversation, with a clear explanation.

It must not silently convert a Scheduled creation flow into an ordinary thread.

Why this is distinct

#34946 requests support for SSH-connected hosts as Scheduled execution targets.

This report focuses on the current UI and state-transition bug: the product accepts a remote target from Scheduled → Create, preserves that target in the resulting conversation, but silently fails to create an automation.

It may also relate to #29128, where the automation update tool is inconsistently absent from Desktop threads.

A reproduction note was previously added to #34946, but this issue tracks the misleading silent fallback as a separate Codex App bug.

Privacy and contact

Hostnames, IP addresses, usernames, company details, internal project names, private paths, and recipient addresses have been omitted.

Contact: liao.yanjun@foxmail.com