Skip to content

When deleting a Codex-managed worktree from Settings, the action feels risky because it is not clear enough whether uncommitted work will be preserved. #25230

@Tiller-Mu

Description

@Tiller-Mu

What variant of Codex are you using?

codex app windows

What feature would you like to see?

Suggested improvements:

  • Show the project/thread/worktree path before deletion
  • Warn clearly if there are uncommitted changes
  • Explain that Codex saves a restorable snapshot
  • Require stronger confirmation for worktrees with uncommitted changes
  • Show a prominent Restore worktree action after deletion

I was able to recover my worktree, but the deletion flow was frightening and could use stronger safety messaging.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appenhancementNew feature or requestsessionIssues involving session (thread) management, resuming, forking, naming, archiving

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions