Add brightness-pilot extension

[giovacalle]

Description

Screencast

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

You can expect an initial review within five business days.

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

[greptile-apps]

PR Summary

New Brightness Pilot extension added for controlling brightness levels across multiple connected monitors, featuring monitor-specific controls and support detection for different display types.

• Empty brightness-cli binary in assets folder is concerning as it's a critical component for monitor control functionality
• Uses synchronous execution (execSync) in src/utils/get-monitors.ts which could block the main thread
• Security concern: Executes an unbundled CLI tool from assets without proper validation or integrity checks
• showToast used for success/failure states instead of the recommended showFailureToast from @raycast/utils in MonitorListItem.tsx
• Race condition potential in MonitorListItem.tsx with async brightness updates

_{13 files reviewed, 1 comment
Edit PR Review Bot Settings | Greptile}

[LitoMore]

Can you check the existing extension https://www.raycast.com/cali/brightness-control?

It looks like we already have an extension for adjusting brightness.

[giovacalle]

I checked the extension you mentioned, but its implementation differs. The one in the Store uses an AppleScript to “press” the brightness keys, whereas my proposed version uses a Swift-based CLI to set brightness levels directly—supporting both built-in (MacBook) and external displays.

I wasn’t sure whether we should merge these into a single extension—especially given the guidance under “When you should consider creating a new extension instead of contributing to an existing one” in the Spotify Controls example (prepare-an-extension-for-store).

This is my first Raycast extension, so I’m happy to hear any advice or best practices you might have :)