Add where-is-my-cursor extension

[luciodaou]

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

Due to our current reduced availability during summer, 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.

[luciodaou]

It dims the screen where is the cursors at. Only a small radius is not dimmed, so it's easy to locate the cursor.
Very useful on multiple monitors.
Basically a very simple copy of Windows PowerToys feature.

[greptile-apps]

Greptile Summary

This PR introduces a new "Where is my Cursor?" extension that provides a visual aid to help users locate their cursor on screen, particularly useful in multi-monitor setups. The extension consists of a single no-view command that executes a Swift binary (LocateCursor) located in the assets folder. When triggered, the Swift application dims the entire screen except for a clear circular area around the cursor position, making it easy to spot.

The implementation includes several key files: a package.json defining the extension metadata and single command, a main TypeScript file (where-is-my-cursor.ts) that executes the Swift binary using Node's exec() function, and the Swift source code (LocateCursor.swift) that creates an overlay window with semi-transparent dimming effects. The Swift implementation handles multi-screen environments by detecting which screen contains the cursor and creates a borderless, mouse-transparent overlay that automatically disappears after 1 second.

This extension addresses a common accessibility need where users lose track of their cursor, especially on large displays or multiple monitors. The approach of using a compiled Swift binary allows for system-level access to screen overlay functionality and cursor positioning that would be difficult to achieve through standard web technologies.

Confidence score: 0/5

• This PR contains critical security and compliance violations that make it unsafe to merge
• Score reflects the inclusion of a compiled binary executable and missing required files for new extensions
• Pay immediate attention to the binary executable in assets folder and missing metadata screenshots

Critical Issues Identified:

1. Binary Executable Violation: The PR includes a compiled binary file (assets/LocateCursor) which violates Raycast extension guidelines. Extensions should not include compiled binaries as they cannot be audited for security, may not work across different architectures, and pose significant security risks.

2. Missing Required Files:

   • No .prettierrc file with required Raycast code style (printWidth: 120, singleQuote: false)
   • Missing metadata folder with screenshots (required for new extensions per guidelines)
   • Empty main.tsx file that should contain the primary command implementation

3. Improper Error Handling: The where-is-my-cursor.ts file uses exec() without proper async/await handling, which could lead to race conditions and doesn't wait for command completion.

4. PR Description Issues: The PR description is missing the required description explaining what the extension does and lacks a screencast/screenshot.

Additional Concerns:

• The Swift code uses hardcoded values (radius: 80, opacity: 0.8, duration: 1 second) that could be made configurable
• No validation that the binary exists or has proper execution permissions
• The approach bypasses Raycast's standard extension architecture

Context used:

Rule - Extensions must include at least one screenshot in a metadata folder for store submission. (link)
Rule - Extensions must include at least one screenshot in a metadata folder for store submission. (link)
Context - In Raycast extensions, ensure to use a consistent configuration for Prettier, specifically 'printWidth: 120' and 'singleQuote: false'. (link)

_{9 files reviewed, 2 comments}

_{Edit Code Review Bot Settings | Greptile}

[greptile-apps]

logic: The async function doesn't await the exec completion. Consider using a Promise wrapper or execSync for proper async handling.

[greptile-apps]

style: Consider using showFailureToast from @raycast/utils instead of manually creating failure toasts: showFailureToast(error, { title: "Failed to locate cursor" });

Suggested change

	exec(helperPath, (error) => {
	if (error) {
	showToast({
	style: Toast.Style.Failure,
	title: "Failed to locate cursor",
	message: error.message,
	});
	} else {
	showToast({ style: Toast.Style.Success, title: "Cursor located" });
	}
	});
	exec(helperPath, (error) => {
	if (error) {
	showFailureToast(error, { title: "Failed to locate cursor" });
	} else {
	showToast({ style: Toast.Style.Success, title: "Cursor located" });
	}
	});

[pernielsentikaer]

Hi 👋

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/luciodaou/where-is-my-cursor

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@luciodaou).
Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.