suggested_update rows for setup-capable worktree automations open old saved automation

Description

suggested_update cards for setup-capable worktree automations render in the Codex desktop app, but clicking the proposed update row appears to open the existing saved automation instead of an applyable proposal. The saved automation remains paused with the old model.

This blocks the safe path required by the automation tool for worktree automations that preserve or set a local environment setup config.

Environment

• Codex desktop app bundled CLI: codex-cli 0.137.0-alpha.4
• OS: macOS 26.4.1 (25E253)
• Repo type: local Git repository
• Automation type: cron automation
• Execution environment: worktree
• Local environment setup config: present under the project .codex/environments directory

Steps To Reproduce

1. Start with an existing paused cron automation that uses:

• execution_environment = "worktree"
• local_environment_config_path = "<project>/.codex/environments/environment.toml"
• a project cwd under a local Git repository

1. Ask Codex to update the automation to:

• status = ACTIVE
• model = "gpt-5.5"
• preserve the existing schedule, prompt, cwd, reasoning effort, worktree execution, and local environment setup config

1. A direct automation_update mode=update is rejected with:

``text
For safety, automations created by the model cannot immediately run a worktree local environment setup script. Use suggested_create or suggested_update so the user can review and approve the setup-capable automation, or set localEnvironmentConfigPath to null.
``

1. Codex then uses automation_update mode=suggested_update for the same target config.
2. The app renders rows like:

• Proposed update - <automation name>

1. Click a proposed update row in the Codex app.

Expected Behavior

The proposed update row should open a review/apply UI for the proposed target config, or otherwise provide a visible apply/save/approve control.

The proposed config should show the new values, e.g. ACTIVE, gpt-5.5, worktree, preserved cwd/schedule/prompt/reasoning, and the local environment setup config.

After approval, the saved automation should update.

Actual Behavior

Clicking the Proposed update row opens the old saved automation detail instead.

The detail pane still shows:

• Status: Paused
• Model: old model, e.g. GPT-5.4
• Reasoning: Low
• No visible approve/apply/save control for the proposed update

The saved automation TOML remains unchanged after clicking the proposed update row.

Why This Matters

The immediate update path is intentionally blocked for setup-capable worktree automations, so suggested_update is the only safe/reviewable path. If the app renders the suggested update but does not expose a way to apply it, these automations cannot be safely updated without either:

• clearing localEnvironmentConfigPath, which degrades the worktree setup, or
• manually editing Codex automation TOML files, which bypasses the tool safety contract.

Additional Notes

• The local environment config file exists and contains setup/cleanup scripts.
• The suggested updates were rendered for multiple automations with the intended target config.
• No manual automation runs were triggered during reproduction.
• I did not attach raw local session logs because they contain local machine/project context, but I can provide redacted excerpts if useful.

Suggested labels: bug, app, automations.