[Downloads Manager] Add "Copy Path" action to Manage Downloads

[fdarian]

Summary

Adds a "Copy Path" action to the Manage Downloads command. It copies the focused download's absolute path as plain text, separate from the existing "Copy File" action (which puts the file itself on the clipboard).

Shortcut: ⌘⇧. on macOS, Ctrl+Shift+. on Windows.

Resolves #28048

Screencast / Screenshots

n/a — text-only action change

Test plan

• Focus a file in Manage Downloads, run "Copy Path" → clipboard contains the absolute path as a string
• Focus a folder, run "Copy Path" → clipboard contains the folder path
• ⌘⇧. triggers the action
• Existing "Copy File" still copies the file itself (regression check)

[raycastbot]

Thank you for your contribution! 🎉

🔔 @thomaspaulmann @ron-myers @infused-kim @ridemountainpig @nagauta @nmder @clins1994 @0xdhrv @YourMCGeek @dhaydl @hugodemenez you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="downloads-manager-copy-path"
FORK_URL="https://github.com/fdarian/extensions.git"
EXTENSION_NAME="downloads-manager"
REPO_NAME="extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

[greptile-apps]

Greptile Summary

This PR adds a "Copy Path" action to the Manage Downloads command, letting users copy a download's absolute path as plain text — distinct from the existing "Copy File" action that puts the file itself on the clipboard.

• Adds Action.CopyToClipboard with content={download.path} and a ⌘⇧. / Ctrl+Shift+. shortcut; platform keys are correctly capitalized and the shortcut object is properly formatted across multiple lines.
• CHANGELOG entry uses a hardcoded date (2026-05-18) rather than the standard {PR_MERGE_DATE} placeholder required by the repository convention.

Confidence Score: 4/5

The implementation change is minimal and correct; the only issue is a hardcoded release date in the changelog that must be replaced before merge.

The manage-downloads.tsx change is straightforward and well-formed. The changelog entry hard-codes today's date instead of the {PR_MERGE_DATE} placeholder that Raycast's release pipeline populates automatically — this will record the wrong date in the published changelog.

extensions/downloads-manager/CHANGELOG.md — hardcoded date needs to be replaced with {PR_MERGE_DATE}.

Important Files Changed

Filename	Overview
extensions/downloads-manager/CHANGELOG.md	New entry added for the Copy Path action, but uses a hardcoded date (2026-05-18) instead of the required {PR_MERGE_DATE} placeholder.
extensions/downloads-manager/src/manage-downloads.tsx	Adds a Copy Path Action.CopyToClipboard with correct platform capitalization and multi-line shortcut; placed logically after "Copy File" in the first action section.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
extensions/downloads-manager/CHANGELOG.md:3
The changelog entry uses a hardcoded date instead of the `{PR_MERGE_DATE}` placeholder. Raycast auto-populates this value on merge, so a literal date here will be wrong for every release pipeline.

```suggestion
## [Add Copy Path action] - {PR_MERGE_DATE}
```

_{Reviews (3): Last reviewed commit: "Update CHANGELOG.md" | Re-trigger Greptile}

[pernielsentikaer]

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/thomas/downloads-manager

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@fdarian).

Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.

[greptile-apps]

The changelog entry uses a hardcoded date instead of the {PR_MERGE_DATE} placeholder. Raycast auto-populates this value on merge, so a literal date here will be wrong for every release pipeline.

Suggested change

	## [Add Copy Path action] - 2026-05-18
	## [Add Copy Path action] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE}... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/downloads-manager/CHANGELOG.md
Line: 3

Comment:
The changelog entry uses a hardcoded date instead of the `{PR_MERGE_DATE}` placeholder. Raycast auto-populates this value on merge, so a literal date here will be wrong for every release pipeline.

```suggestion
## [Add Copy Path action] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}`... ([source](https://app.greptile.com/review/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

How can I resolve this? If you propose a fix, please make it concise.