Codex Remote: allow downloading workspace files to the local machine

Start with the Codex App Files panel and remote-workspace file preview and context-menu flow described in the issue. Trace how a remote file is selected, then define the transfer workflow for files, multiple selections, and folders, including destination choice, progress, conflicts, permissions, and errors. Done means the expected SSH workflow transfers binary and text deliverables to a chosen local path without requiring scp.

What variant of Codex are you using?

Codex App 26.707.31428 with an SSH-backed Codex Remote project.

What feature would you like to see?

Please add a first-class way to download files and folders from a remote workspace to the local machine running the Codex App.

Today, when a task runs on a connected remote host and produces deliverables, the Files panel and absolute-path links can expose or preview those files, but there is no Download or Save As action that transfers them to the local computer.

Requested behavior:

• Add Download / Save As to remote-workspace file previews and file context menus.
• Allow downloading one file, multiple selected files, or a folder (optionally archived automatically).
• Let the user choose a local destination.
• Show transfer progress, file size, completion state, and actionable errors.
• Handle conflicts with rename, overwrite, or skip choices instead of silently overwriting.
• Respect remote filesystem permissions, Codex sandbox policy, and local write permissions.
• Clearly label the transfer direction as remote host -> local machine.
• Support binary deliverables as well as text files.

Why this is useful

A real task produced four final deliverables on an SSH remote host:

• a PDF report;
• a detached digital signature;
• a public key;
• a PCAP network capture.

The work completed successfully, but the files could not be downloaded through the Codex App. The only working path was to leave the app and run scp manually from one machine to the other.

Remote workflows are incomplete if Codex can create artifacts but the user cannot retrieve them from the same interface. This is especially important for non-code work such as reports, PDFs, archives, datasets, captures, images, videos, and signed documents.

Expected workflow

1. Open a task running on an SSH remote connection.
2. Open the Files panel or click a file link in the conversation.
3. Select Download or Save As.
4. Choose a local destination.
5. Codex transfers the file securely and confirms the saved local path.

This should not require moving or handing off the entire task, configuring a second file-transfer tool, or manually running SSH/SCP commands.

Additional information

Related but distinct: #34203 requests a workspace file editor for connected hosts. This request is specifically about transferring existing remote files and folders to the local machine.