SOLWYN

Installation

Install the Solwyn CLI — requirements, entry points, verification, and its separation from the SDK.

The Solwyn CLI ships as the solwyn-cli package on PyPI. It is a standalone terminal client for the Solwyn Cloud API — a different package from the solwyn Python SDK, with no dependency between them.

Install

Terminal
pip install solwyn-cli
Terminal
uv tool install solwyn-cli

uv tool install puts the CLI on your PATH in its own isolated environment, so it never collides with a project's dependencies.

Requirements

  • Python 3.11 or newer. The package declares requires-python >=3.11; older interpreters are refused at install time.

Two names, one command

Installing exposes two entry points — solwyn and solwyn-cli. They resolve to the same program; use whichever reads better in your shell or scripts. This documentation uses solwyn.

No phone-home

The CLI does not report anything about you or your usage back to Solwyn. There is no telemetry, no update checks, and no phone-home — the only network traffic it originates is the API calls a command explicitly makes on your behalf, using credentials you supplied. It never collects provider keys, prompts, or responses.

Verify your installation

Confirm the version:

Terminal
solwyn --version

It prints the installed version and exits:

Terminal
solwyn 0.1.0

List the available commands:

Terminal
solwyn --help

If both commands print without error, the CLI is installed correctly.

Separate package from the SDK

The CLI and the SDK are distinct packages that do different jobs. You can install both in one environment.

PackageInstall commandWhat it does
solwyn-clipip install solwyn-cliTerminal client that talks to the Solwyn Cloud API.
solwynpip install solwynPython SDK that wraps your LLM provider client.

They have no dependency on each other — installing or upgrading one never pulls in the other.

Next steps

On this page