›_ Codex Issues
Codex Issues / #33217

Codex Desktop: move Archive away from Rename/Pin in task context menu

Open 💬 2 comments Opened Jul 15, 2026 by Jason-Wang313

What happened?

In Codex Desktop, when right-clicking a task/session in the sidebar, the context menu places Archive very close to common non-destructive actions like Rename and Pin.

This makes it easy to accidentally archive a task when the intended action is just to rename or pin it. I have already mispressed Archive while trying to use Rename.

Why this is a problem

Archive is a higher-impact action than Rename or Pin because it removes the task from the active sidebar flow. Even if it can be undone or found later, an accidental archive is disruptive and surprising compared with the nearby actions.

Expected behavior

Please separate Archive from lower-risk actions such as Rename and Pin in the task/session right-click menu. Possible fixes:

  • Put Archive in a separate menu group with a divider.
  • Move Archive farther away from Rename and Pin.
  • Place destructive or visibility-changing actions near the bottom of the menu.
  • Consider an undo affordance after archiving, if not already present.

Environment

  • Product: Codex Desktop app
  • Area: Sidebar task/session right-click context menu

View original on GitHub ↗

2 Comments

Jason-Wang313 · 1 month ago

Additional related UX request: the right-click context menu itself feels slightly too small in Codex Desktop.

Making the menu a bit larger, for example with larger text, more padding, and/or taller menu rows, would make each action easier to read and target. That should reduce both misreading and accidental clicks, especially for adjacent actions like Rename, Pin, and Archive.

Lin-Guanguo · 17 days ago

Adding a macOS reproduction where the impact is substantially worse for managed-worktree tasks.

Important clarification: this was not the right-click/context menu described in the issue body. It was the left sidebar task list itself. Each task row exposes Pin and Archive as two adjacent inline buttons on the right side of the row. I intended to click Pin and hit Archive instead.

The inline placement itself is reasonable and convenient. My primary request is not necessarily to remove or relocate the Archive button. The problem is that Archive executes immediately with no confirmation even when it triggers a filesystem cleanup that Undo cannot restore.

Environment:

  • Codex Desktop 26.803.61601 (build 6396)
  • macOS
  • Remote SSH task with a Codex-managed worktree

Observed behavior:

  1. A single click on the inline Archive button executed immediately. There was no confirmation dialog or second confirmation step.
  2. The only visible feedback was an Undo toast.
  3. Archiving cleaned up the managed worktree.
  4. Undo/unarchive restored the thread's archive metadata, but did not recreate the deleted worktree.
  5. Resuming the restored task then failed because its original working directory no longer existed.

This means the current Undo affordance is misleading for managed-worktree tasks: the visible archive state is reversible, but the filesystem side effect is not. What looks like a minor accidental click can interrupt a long-running task and discard uncommitted work.

Requested UX/safety changes:

  • Keep the inline Archive action if desired, but require a blocking, title-specific confirmation whenever archiving will remove a managed worktree.
  • Explicitly warn that the managed worktree will be removed and that uncommitted changes may be lost.
  • Ideally show whether the worktree is clean before allowing cleanup.
  • Either make Undo restore/cancel worktree cleanup too, or do not present the operation as fully reversible.
  • If Archive becomes metadata-only and truly reversible, an Undo toast would be sufficient; it is not sufficient for the current cleanup behavior.

Related accidental-archive UX report: #30230.
Related recovery reports: #10917 and #12166.