# Installation Source: https://alysiscode.com/docs/getting-started/installation Install the `alysis-code` Python package to use Alysis in your terminal. Both `alysis` and `alysis-code` launch the TUI. ## Install on Linux, macOS, or WSL The shell installer creates an isolated uv tool environment with its own Python: ```bash curl -LsSf https://raw.githubusercontent.com/AlysisAi/AlysisCode/main/scripts/install.sh | sh ``` You can [read the installer](https://github.com/AlysisAi/AlysisCode/blob/main/scripts/install.sh) before running it. It installs uv if needed and does not replace your system Python. Open a new terminal when it finishes. If you already use uv or pipx with Python 3.11 or newer, choose one: ```bash uv tool install alysis-code ``` ```bash pipx install alysis-code ``` Use your operating system's package manager to install pipx if needed, then run `pipx ensurepath`. If the default Python is too old, use `pipx install --python python3.12 alysis-code`. ## Windows In Windows PowerShell 5.1 or PowerShell 7, the installer can set up uv and Python 3.12 for you: ```powershell irm https://raw.githubusercontent.com/AlysisAi/AlysisCode/main/scripts/install.ps1 | iex ``` You can [read the PowerShell installer](https://github.com/AlysisAi/AlysisCode/blob/main/scripts/install.ps1) first. It needs no administrator access and makes `alysis` available in the current terminal. Restart other open terminals if needed. Run the installer again to upgrade. Set `ALYSIS_VERSION` to pin a release, `ALYSIS_PYTHON` to choose Python, or `ALYSIS_NO_MODIFY_PATH=1` to skip persistent PATH changes. Sandbox support depends on the installed release; see the native Windows requirements below or use Docker. For native Windows, use a release that includes the bundled Windows x64 sandbox. With uv installed: ```powershell uv tool install --python 3.12 --link-mode copy alysis-code alysis sandbox doctor --smoke ``` The copy link mode avoids shared package-cache hardlinks that the contained file worker cannot use. For an existing uv installation, use `uv tool install --reinstall --link-mode copy alysis-code`. pipx is another option; the standalone Windows executable includes its own runtime. The native sandbox is in beta. It needs a compatible Windows x64 system and local fixed NTFS folders. It runs PowerShell commands without requiring Docker or the desktop app. Full access instead uses the host runner with `cmd.exe` semantics. Check the [Windows installation reference](https://github.com/AlysisAi/AlysisCode/blob/main/docs/windows-cli-sandbox.md) for supported paths and limits. For WSL, run this in PowerShell, restart if asked, then open your Linux distribution and use the Linux installer: ```powershell wsl --install ``` Keep Linux projects under a Linux path such as `~/projects`. WSL uses Linux sandbox backends; it does not use the native Windows helper. Keep the two Python environments separate. ## Verify and start ```bash alysis --version alysis --help cd your-project alysis ``` The first launch opens setup for a provider connection, model, workspace, and sandbox. Reopen it with `alysis setup`. ## Connect your Alysis account ```sh alysis --version alysis login ``` Approve the short code in your browser to connect this machine to your account and credits. Version 0.15.2 or newer supports hosted login without cloud environment variables. If 0.15.1 reports that hosted services are not configured, run `alysis update` or `pipx upgrade alysis-code`, then retry. You can also configure your own provider in setup; that path does not require an Alysis account. ## Check the sandbox ```bash alysis sandbox setup alysis sandbox doctor --smoke ``` For Docker, start the daemon and pull the configured image when needed: ```bash alysis sandbox pull ``` Docker needs a running daemon and the configured image. If the smoke check fails, follow [sandbox setup](/docs/safety/sandbox-modes). ## Optional extras Install document libraries for document, workbook, presentation, and PDF operations: ```bash uv tool install --upgrade "alysis-code[documents]" ``` Use `alysis-code[server]` when the installation needs the HTTP server. The packaged desktop app already includes its managed engine and document dependencies; see [desktop installation](/docs/desktop/installation). ## Older installations If you're upgrading an older Sylliptor installation, back up its configuration first. Old command aliases and automatic migration may no longer work. Check which package supplies your executable, then use the current Alysis commands. Continue with [your first TUI task](/docs/getting-started/first-run) or [updating the TUI](/docs/cli/update).