Add fetch extension

[chrismessina]

Description

Fetch is a new extension for downloading files from Raycast — one URL, a list of them, or a curl-style numbered range. Downloads are handed to a background process that outlives the command, so dismissing the Raycast window doesn't cancel a transfer in progress, and an interrupted download can resume rather than starting over.

It shells out to curl, which ships with macOS, so there is nothing for a user to install.

Changes

• Download — a single file from a URL argument or the clipboard, with live progress in a toast and Show in Finder on completion. Filenames come from Content-Disposition when the server sends one, falling back to the URL path, and gain the right extension from the content type when the URL has none.
• Download Batch — many files at once with a per-file progress list. Accepts one URL per line, URLs embedded in prose, and markdown links, with duplicates removed. Imports open browser tabs via the Raycast browser extension. Individual downloads and the whole batch can be cancelled, and failures retried.

• Download History — the last 100 downloads, with open, reveal, copy URL, copy path, and re-download. Failed entries keep their error message. Entries can be deleted individually, by age, or all at once.

• Range patterns — file[001-025].zip expands into one download per number, with zero-padding inferred from the start value and descending ranges supported. Capped at 500 URLs, with a preview before submitting.
• Preferences — output directory, overwrite behaviour, redirect following, stall timeout, parallel download limit, and debug logging.

Colliding filenames are resolved by reserving each output path on the filesystem before the transfer starts, so two files in one batch can never be handed the same name.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

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

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Confidence Score: 4/5

The PR is not ready to merge until the changelog placeholder is restored.

Findings

1.  Restore the merge-date placeholder ▶

Fix with agent prompt

### Issue 1
extensions/fetch/CHANGELOG.md:3
This replaces `{PR_MERGE_DATE}` with a fixed date. The changelog rule requires the placeholder so the release flow can insert the actual merge date. Restore `{PR_MERGE_DATE}` here.

```suggestion
## [Initial Version] - {PR_MERGE_DATE}
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Fetch adds a Raycast extension for downloading one or many files from URLs, clipboard text, browser tabs, and numbered ranges. Transfers run in the background with progress, cancellation, resume support, collision-safe filenames, and a history that can be managed later.

• Adds single-file downloads with header-based filenames and completion actions.
• Adds batch downloads with URL extraction, range expansion, parallel progress, cancellation, and retries.
• Adds persistent download history and configurable download preferences.

_{Reviews (5) · Last reviewed commit: "Update CHANGELOG.md and optimise images"}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/chrismessina/fetch

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.

[greptile-apps]

This replaces {PR_MERGE_DATE} with a fixed date. The changelog rule requires the placeholder so the release flow can insert the actual merge date. Restore {PR_MERGE_DATE} here.

Suggested change

	## [Initial Version] - 2026-09-24
	## [Initial Version] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE} placeholder in titles, be placed at the top of the file, and maintain descending version order. Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... (source)

Prompt To Fix With AI

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

Comment:
This replaces `{PR_MERGE_DATE}` with a fixed date. The changelog rule requires the placeholder so the release flow can insert the actual merge date. Restore `{PR_MERGE_DATE}` here.

```suggestion
## [Initial Version] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}` placeholder in titles, be placed at the top of the file, and maintain descending version order.  Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... ([source](https://app.greptile.com/raycast/-/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.