Add screenshots extension

[elliotekj]

Description

A screenshot browser for quick find-and-paste of screenshots into the foreground app. Built with Claude Code, Codex, etc in mind but works for anything that accepts pasted images.

Screencast

screenshots_demo.mov

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! 🚀

Due to our current reduced availability, the initial review may take up to 10-15 business days.

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

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds a new Screenshots extension that provides a grid-based browser for macOS screenshots with a paste-first workflow. The extension automatically detects the screenshot directory from macOS system preferences, watches for new screenshots, and supports infinite scrolling.

Key Features:

• Grid view with thumbnail previews sorted by modification time
• Auto-detection of screenshot directory (preference → system location → Desktop fallback)
• Real-time directory watching for auto-refresh
• Paste action that copies to clipboard and simulates Cmd+V
• Standard file operations (copy, preview, open, reveal, trash)
• Infinite scroll with batched loading (20 items at a time)

Architecture:

• Uses fs.watch for directory monitoring with automatic cleanup
• Custom useScreenshots hook manages loading state and pagination
• Leverages image-size package for dimension extraction
• Properly uses Action.Trash for deletion
• Correctly relies on auto-generated Preferences interface

Confidence Score: 4/5

• Generally safe to merge with one logic issue that may affect user experience during paste operations
• The extension follows Raycast conventions well (uses Action.Trash, auto-generated Preferences, includes metadata screenshots, has CHANGELOG). However, the use of blocking execSync in an async function (line 172) can freeze the UI during paste operations, which is a real UX issue. The "latest" dependency version is a minor maintainability concern but not blocking.
• extensions/screenshots/src/browse-screenshots.tsx - contains blocking execSync call that should be made async

Important Files Changed

File Analysis

Filename	Score	Overview
extensions/screenshots/package.json	4/5	New extension manifest with standard configuration. Uses "latest" for @raycast/api instead of semantic version.
extensions/screenshots/src/browse-screenshots.tsx	3/5	Main extension code with screenshot browsing/paste functionality. Uses blocking execSync in async context.
extensions/screenshots/README.md	5/5	Well-structured documentation with feature list and configuration instructions.
extensions/screenshots/CHANGELOG.md	5/5	Comprehensive initial release changelog following conventions.

[greptile-apps]

_{2 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Use a specific semantic version instead of "latest" for @raycast/api. The "latest" tag can cause unpredictable behavior and breaks reproducible builds. Other extensions in this repo use versions like "^1.104.1" or similar.

[greptile-apps]

execSync blocks the Node.js event loop, which can freeze the Raycast UI during the paste operation. Use async exec with promisify instead for non-blocking execution in this async function.

[ridemountainpig]

Is this extension different from the Search Screenshots command? They look similar.

[0xdhrv]

Thanks for your contribution @elliotekj 🔥

We already have multiple extensions in the Store that deal with JWT. Could we consider enhancing one of the existing extensions below instead of creating another one?

• Screenshot — by @Aayush9029
• Search Screenshot — inbuilt command

If there are unique features or workflows you’re aiming to add, we’d love to hear them and see if they can be integrated into one of these to avoid duplication and improve discoverability.

This would help avoid duplication and keep related functionality consolidated in one place.
As mentioned in our extension guidelines here ↗