# Tools and runtimes

Help Orbit find your development tools, or choose a specific installed version.

These settings are for features that use development tools installed on your Mac, such as dependency checks. You do not need to configure them to use projects, tasks, notes, or files.

## Automatic detection

Orbit detects supported runtimes and package tools automatically. Open **Settings → Tools & runtimes** to inspect PHP, Node, Composer, npm, pnpm, and Yarn. Use **Check paths** to inspect the current configuration and show each tool's state, version, and resolved executable.

The packaged app includes what Orbit itself needs. Source operations may still need tools installed on your computer, such as Git for cloning and the appropriate package tools for dependency checks.

## Set a workspace override

1. Expand the runtime you want to configure.
2. Enter its executable path or use **Browse**.
3. Select **Check paths** and review the resolved version and path.
4. Select **Save changes**.
5. Rerun the relevant project scan or dependency check.

Choose an installed executable or package-manager entry file. Shell wrappers are unsupported. If a command works in an interactive terminal but Orbit cannot find it, an explicit path can avoid differences in the app's environment.

## Package-location overrides

For a project that needs a different version, open **Dependencies → Manage locations → Location settings → Advanced: executable overrides**. A location's entered override takes priority over the workspace default. Blank values inherit workspace settings and automatic detection.

Closing Advanced does not disable an override. Clear its field and save to use the workspace setting again. After changing a location's paths, save and rerun its dependency check.

## Troubleshoot tool errors

If a path is missing, choose the current installed executable. If it points to a wrapper, use the underlying supported executable or entry file. If a version manager moved a path, update the override and save.

A successful path check does not rerun earlier dependency checks automatically. Saved runtime changes apply on the next scan. Read the package location's coverage and error messages after checking again.