# Environment

A command only works in Solo if it starts with the environment it expects. Learn where Solo gets PATH and shell variables, how execution profiles change command startup, and what to check when a language version manager is involved.

## Pages

- [Shell environment](/api/v1/docs/environment/shell-environment) - On macOS and Linux, Solo captures your login shell environment so newly launched PTY-backed terminals, commands, and agents receive the captured PATH, version-manager exports, and…
- [Execution profiles](/api/v1/docs/environment/execution-profiles) - An execution profile decides which shell — and, on Windows, which environment — Solo uses for a project's commands and agents, and for terminals that inherit the project profile. A…
- [Version managers](/api/v1/docs/environment/version-managers) - On macOS and other Unix-like hosts, Solo works with shell-configured version managers by capturing your login shell environment. If that shell adds a version manager to PATH, an ex…

---

Are you a human? Read this doc on the web: https://soloterm.com/docs/environment