Add cloudflare-images extension

[mcdays94]

Description

Cloudflare Images uploader for Raycast: clipboard-first uploads, multi-select Finder uploads, and an in-Raycast browser for the images already in your Cloudflare Images account.

Inspired by, and a sibling of, my own cloudflare-images-upload VS Code / Cursor / Windsurf extension (also on Open VSX, VS Code username miguelcaetanodias, Raycast username miguel_caetano_dias — same author). The VS Code original uses documentPasteEdits / documentDropEdits to intercept paste and drop inside the editor. This Raycast port brings the same workflow next to the editor so it works in every Mac app, including Zed and other editors that don't expose those VS Code-specific APIs.

Eleven commands grouped under "Cloudflare Images"

• Setup: Validate Cloudflare Credentials, Set Default Variant (live variant picker from the user's CF account)
• Upload from clipboard: Upload Clipboard Image (preference-driven, with optional format dropdown argument) + format-locked variants Upload Clipboard as Markdown / as HTML / as URL
• Upload from Finder: Upload Selected File (handles multi-select sequentially with per-file progress + partial-failure tolerance) + format-locked variants
• Manage: My Cloudflare Images (list view with thumbnails, keyword search across filename + image ID + custom metadata, detail panel via ⌘ D, destructive-confirm delete)

Feature parity with the VS Code extension

SHA-256 dedupe cache (Raycast LocalStorage, 30-day TTL), sharp-based compression with progressive quality reduction, AVIF → WebP/JPEG/PNG conversion before upload, HMAC-signed URLs with auto-fetched (or manually-overridden) signing key, metadata templating with eight ${...} placeholders. The only VS Code features intentionally dropped are the ones the Raycast extension model can't expose: drag-drop INTO the editor, language-aware paste formatting, and delete-on-removal from documents.

Architecture

Monorepo at https://github.com/mcdays94/cloudflare-images-tools. The Raycast extension consumes a shared TypeScript core published to npm as @mcdays/cloudflare-images-core@0.0.1, so the same logic will be reusable by a planned MCP server (for Zed / Claude Code / Cursor). The core has no editor or Raycast assumptions — it's just the pure upload / dedupe / signed-URL / compression / variants / list / delete / metadata-templating logic.

Screencast

Three still screenshots are attached in metadata/:

1. cloudflare-images-1.png — My Cloudflare Images list view with thumbnails
2. cloudflare-images-2.png — My Cloudflare Images detail panel (⌘ D) showing metadata
3. cloudflare-images-3.png — Set Default Variant live picker

The headline workflow is brief enough that stills capture it: copy image → Raycast → "Upload Clipboard Image" → URL pasted at cursor in the previously-focused app. Happy to add a screencast if the reviewer prefers — let me know.

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 (only icon.png is shipped in assets/)
• I checked that assets used by the README are placed outside of the metadata folder (the per-package README references assets/icon.png; metadata/ contains only the Store screenshots)

[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]

Greptile Summary

This PR introduces a new Cloudflare Images Raycast extension with 21 commands covering clipboard and Finder uploads, a browsable image list, signed-URL support, SHA-256 deduplication, sharp-based compression, AVIF conversion, and rich metadata templating. The shared upload logic lives in an external npm package (@mcdays/cloudflare-images-core) so no upload or signing logic is duplicated across the many command entry points.

• All 21 commands delegate to two shared implementations (runUploadClipboard / runUploadFinder), keeping behavior consistent across format-locked and signed-locked hotkey variants.
• my-images.tsx exposes a Refresh Signing Key action that explicitly clears the cached key and re-fetches — addressing the key-rotation recovery gap noted in a prior review cycle.
• CHANGELOG.md uses a hard-coded date (2026-06-10) instead of the required {PR_MERGE_DATE} placeholder, and the metadata/ folder is missing the cloudflare-images-2.png screenshot described in the PR.

Confidence Score: 5/5

Safe to merge once the changelog placeholder and the missing screenshot are addressed; the core upload, signing, and caching logic is well-structured and defensive.

The extension is a net-new addition with no impact on existing code. Upload pipelines handle errors gracefully, the dedup cache has TTL and migration logic, signed-URL rotation is recoverable through the exposed action, and credentials are validated before any network call. The two open items are a changelog formatting convention and a missing metadata image — neither affects runtime behaviour.

CHANGELOG.md (hardcoded date) and the missing metadata/cloudflare-images-2.png screenshot.

Important Files Changed

Filename	Overview
extensions/cloudflare-images/CHANGELOG.md	Initial release entry uses a hardcoded date 2026-06-10 instead of the required {PR_MERGE_DATE} template variable.
extensions/cloudflare-images/src/lib/upload-clipboard-impl.ts	Core clipboard upload pipeline — handles clipboard reading (file ref, text path, osascript PNG dump), deduplication, compression, and signed-URL signing. Well-structured; temp file is cleaned via finally block.
extensions/cloudflare-images/src/lib/upload-finder-impl.ts	Finder multi-select upload pipeline with partial-failure tolerance; clean structure mirroring the clipboard impl.
extensions/cloudflare-images/src/my-images.tsx	Image browser with thumbnail list, detail panel, metadata keyword search, signed-URL handling, and destructive-confirm delete. Logic is sound.
extensions/cloudflare-images/src/lib/signing-key.ts	Signing key resolution with manual-override, LocalStorage cache, and API auto-fetch; clearCachedSigningKey exposed and wired to Refresh Signing Key action in my-images.tsx.
extensions/cloudflare-images/src/lib/config.ts	Preference reading and config-building helpers; CfImagesPreferences = Preferences alias (addressed from prior review). Numeric textfields parsed with proper clamping helpers.
extensions/cloudflare-images/src/lib/cache.ts	30-day TTL SHA-256 dedup cache with legacy v0.2.1 migration path for URL-only entries.
extensions/cloudflare-images/package.json	21-command manifest with correct $schema, categories, platforms, and preference definitions; @raycast/utils removed (addressed from prior review).
extensions/cloudflare-images/eslint.config.js	Correctly uses defineConfig from eslint/config with the Raycast preset (addressed from prior review).
extensions/cloudflare-images/src/validate-credentials.tsx	Credential validation view with detailed per-failure-reason Markdown output and actionable retry/prefs actions.

Prompt To Fix All With AI

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

---

### Issue 1 of 2
extensions/cloudflare-images/CHANGELOG.md:7
The initial release entry uses a hard-coded date rather than the `{PR_MERGE_DATE}` template variable required by this repo's changelog convention. If the PR merges on a different calendar day the date will be wrong, and the Raycast tooling expects the placeholder so it can substitute the actual merge date automatically.

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

### Issue 2 of 2
extensions/cloudflare-images/metadata/cloudflare-images-1.png:?
**Screenshot #2 referenced in PR description but not committed**

The PR description lists three screenshots — `cloudflare-images-1.png`, `cloudflare-images-2.png` (detail panel), and `cloudflare-images-3.png` — but only #1 and #3 appear in the diff. The `metadata/` folder is missing `cloudflare-images-2.png`. Store reviewers may notice the gap, and the detail panel screenshot is the one that best showcases the metadata feature.

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

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[0xdhrv]

suggestion (non-blocking): Remove the metadata screenshot

This screenshot seems redundant since the commands are already listed as a separate tab on the store page.

[0xdhrv]

suggestion (non-blocking): Keep the changelog entry user-focused

This initial version should probably contain just one changelog entry. The current wording feels a bit more like a dev update, so it might be clearer to frame it in terms of what changes for end users.

[0xdhrv]

Hey @mcdays94 👋

I have added a few comments for you to address.

I'm looking forward to testing this extension again 🔥

Feel free to contact me here or at Slack if you have any questions.

---

I converted this PR into a draft until it's ready for the review, please press the button Ready for review when it's ready and we'll have a look 😊

[greptile-apps]

Want your agent to iterate on Greptile's feedback? Try greploops.

[greptile-apps]

Signing key cached indefinitely — no recovery path after key rotation

The signing key is written to LocalStorage at line 50 with no TTL, and there is no UI-accessible action that calls clearCachedSigningKey. If a user rotates their Cloudflare signing key (which CF supports via the dashboard's "Rotate signing key" feature), the extension will permanently serve the stale key, silently generating HMAC-signed URLs that 404. The only workarounds are setting manualSigningKey in preferences or clearing Raycast's LocalStorage externally — neither is obvious from inside the extension.

Consider adding a fixed TTL (e.g., 7 days) to the LocalStorage entry, or exposing a "Refresh Signing Key" action in the My Cloudflare Images action panel (similar to the "Reload List" action already there) so users have a recovery path.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/cloudflare-images/src/lib/signing-key.ts
Line: 43-51

Comment:
**Signing key cached indefinitely — no recovery path after key rotation**

The signing key is written to LocalStorage at line 50 with no TTL, and there is no UI-accessible action that calls `clearCachedSigningKey`. If a user rotates their Cloudflare signing key (which CF supports via the dashboard's "Rotate signing key" feature), the extension will permanently serve the stale key, silently generating HMAC-signed URLs that 404. The only workarounds are setting `manualSigningKey` in preferences or clearing Raycast's LocalStorage externally — neither is obvious from inside the extension.

Consider adding a fixed TTL (e.g., 7 days) to the LocalStorage entry, or exposing a "Refresh Signing Key" action in the `My Cloudflare Images` action panel (similar to the "Reload List" action already there) so users have a recovery path.

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

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/miguel_caetano_dias/cloudflare-images

[raycastbot]

🎉 🎉 🎉

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