Add mise extension

[lachieh]

Description

Raycast commands for mise (mise-en-place), the dev-tool version manager by @jdx

• Search Tools — mise's registry plus npm:, cargo: and gem: package search; installs go to your global config (mise use -g, or a chosen config file).
• Show Installed Tools — versions, active version, source file; set the global version, upgrade, uninstall.
• Show Outdated Tools / Tools Menu Bar — what mise outdated reports, with one-click upgrades; the menu bar refreshes every 12 hours.
• Upgrade All Tools, Prune Unused Versions, Clear Cache — the corresponding mise commands with progress toasts.
• Manage Tasks — global mise tasks, run in your terminal or with captured output.

All commands operate on global mise configuration, which is what applies when Raycast has no project directory. mise itself is not bundled: the extension finds the user's binary (preference, standard paths, or their login shell) and runs it with the login shell's environment so exports like CARGO_HOME apply as they do in a terminal. Nothing is downloaded or executed with a shell; every mise call is execFile/spawn with an argument array.

Notes for review

• npm run lint runs oxlint and oxfmt (the repository's day-to-day tooling); @raycast/eslint-config and Prettier are installed with Raycast's standard settings, and npx ray lint passes (ESLint and Prettier both run) — it is simply not wired into the npm scripts.
• Tests: npm test (unit + component tests behind a small @raycast/api stub) and npm run test:integration (dry-runs every mise command line against a real mise).
• Screenshots pass scripts/check_raycast_images.py and scripts/check_metadata_images.py locally.

Screencast

Screenshots of each command are in metadata/ (Search Tools with a backend query, Show Installed Tools with details, Show Outdated Tools, Manage Tasks, the version picker).

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 safe to merge until the open remove flow is fixed.

Findings

1.  This import points to src/ui/useDebounced , but that file is not in the branch, so Search Tools cannot compile. The new operations.test.ts also reads fixtures/use-low-downloads-stderr.txt , which is missing. Add both files or remove these references before merging. ▶
2.  remove runs unuse first and only runs uninstall --all after success. The installed list keeps tools with no active config, and Search Tools still gives those rows this Remove action. For such a tool, unuse fails because there is no config entry, so the runner stops before deleting any installed version. Skip unuse when no config declares the tool, or still run the uninstall step for that specific failure. ▶

Fix with agent prompt

### Issue 1
extensions/mise/src/search-tools.tsx:undefined-19
This import points to `src/ui/useDebounced`, but that file is not in the branch, so `Search Tools` cannot compile. The new `operations.test.ts` also reads `fixtures/use-low-downloads-stderr.txt`, which is missing. Add both files or remove these references before merging.

### Issue 2
extensions/mise/src/mise/operations.ts:93-94
`remove` runs `unuse` first and only runs `uninstall --all` after success. The installed list keeps tools with no active config, and `Search Tools` still gives those rows this Remove action. For such a tool, `unuse` fails because there is no config entry, so the runner stops before deleting any installed version. Skip `unuse` when no config declares the tool, or still run the uninstall step for that specific failure.

---

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

Summary

Adds a macOS Raycast extension for managing mise tools and global tasks. It finds mise through preferences, common paths, or the login shell, then runs mise commands without a shell while supporting search, installs, upgrades, cleanup, outdated checks, and task output.

_{Reviews (4) · Last reviewed commit: "Add the debounce hook and low-downloads ..."}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​types/​react-test-renderer@​19.0.0
	npm/​vitest@​5.0.1
	npm/​react-test-renderer@​19.0.0
	npm/​oxfmt@​0.68.0
	npm/​oxlint@​1.83.0

View full report

[0xdhrv]

Hey @lachieh 👋

Thanks for your contribution 🔥 This is a really thorough mise client — careful execFile/spawn usage, login-shell env probing, solid prefs, and a serious test suite.

Here's everything I found in this pass:

Blocking

• issue (blocking): In Search Tools, Remove always runs mise unuse <tool> and only then mise uninstall --all <tool> (remove + runOperation's andThen). Installed tools with no config entry (inactive) make unuse fail, so uninstall never runs and nothing is deleted.

Please either:

• only offer Remove when a version has a config source, and use uninstall-only for inactive tools, or

• change remove so uninstall still runs when unuse fails because there is no config entry

• issue (blocking): metadata/mise-3.png shows personal paths under /Users/lachlan/…. Please retake it with the Capture Window command (tick Save to Metadata) using mock data so the home directory isn’t identifiable.

Docs: https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots

Should fix

• issue: In outdated-tools.tsx, launchCommand for Show Outdated Tools isn’t wrapped. It can throw if that command is disabled. Please catch it:

try {
  await launchCommand({ name: "show-outdated", type: LaunchType.UserInitiated, context: upgrade ? { upgrade } : undefined });
} catch (error) {
  await showFailureToast(error, { title: "Could not open Show Outdated Tools" });
}

Optional

• suggestion: You can simplify some failure toasts with showFailureToast(error) from @raycast/utils (e.g. in runInTerminal / generic failure paths).

When the blocking items are done, press Ready for review. I've converted the PR to a draft until then 😊

Feel free to reach me here or on Slack if anything is unclear.