data/sessions/explorer-copy-to-folder-3/memory.md

Memory: explorer-copy-to-folder-3

Overview

Copy a file into a subfolder from a shell. Use this as the terminal route to the same end state as the file-manager copy: one command names the source and the destination folder, the original is left in place, and no window or selection is involved. The recorded trace opens a shell, copies report.pdf into dest\, and closes the shell with exit.

Prerequisites

• A desktop environment with a file manager, or a shell.
• A file to copy and a destination folder, both existing before the task starts and both identifiable by name.
• Write access to the destination folder, and read access to the file.
• Enough free space at the destination for a second copy.
• Clarity that the result is a copy, not a move. The original must still be in place when the task finishes; a route that leaves the source folder empty has done a different job.
• No file of the same name already in the destination. Both routes overwrite — the shell without asking, the file manager after a confirmation that is easy to accept reflexively.

Steps

Step 1 — Left-click at (268, 1060)

The task is to copy a file into a subfolder while leaving the original in place, which is a single copy command, so the first move is to open a shell. Move the cursor and Left-click the PowerShell icon in the taskbar.

Step 2 — Type: Copy-Item $env:USERPROFILE\corpus-seed\report.pdf $env:USERPROFILE\corpus-seed\dest\

Type a Copy-Item command naming the source file and the destination folder. Copy-Item leaves the source in place, which is the whole difference between this task and the move task. The destination ends in a backslash, naming a directory rather than a new filename, so the file keeps its own name inside dest.

Step 3 — Press: Enter

After typing the command Press Enter to run the copy.

Step 4 — Type: exit

Type exit to close the shell.

Step 5 — Press: Enter

After typing the exit Press Enter to run it and close the window.

Notes & Edge Cases

1. The trailing separator on the destination is the safety feature. With it the command expects a directory; without it, a destination that does not exist is treated as a filename and the file is copied to a file of that name instead of into a folder — a failure that reports nothing and looks nothing like what was asked for.
2. The copy overwrites a same-named file at the destination without asking. Check first, or use the option that refuses to replace.
3. The command copies a file, not a directory. Copying a folder needs the recursive option, and the trailing separator then changes what the result ends up nested inside — worth testing on something disposable first.
4. The original is untouched, which is the whole distinction from a move. The command that moves is one word different and produces an identical-looking destination, so confirm the source still exists.
5. Absolute paths built from the environment variable keep the command independent of the shell's current directory, which is unknown in a freshly opened window and is exactly where this kind of command gets typed.
6. The environment variable is expanded by the shell, so the same string handed to something that is not a shell leaves the literal text unresolved.
7. The prompt returning is not confirmation that the file arrived. Check the destination before treating the task as done.