Use Presolve from the command line.

Install the released Presolve CLI.

macOS or Linux

curl -fsSL https://presolve.dev/install.sh | sh
presolve --version

The installer selects the native archive for your operating system and CPU architecture, verifies its SHA-256 checksum, installs it under ~/.presolve/bin, and adds that directory to your shell PATH when necessary.

Windows PowerShell

irm https://presolve.dev/install.ps1 | iex
presolve --version

The Windows installer downloads the x86_64 native archive, verifies its checksum, installs presolve.exe under your user profile, and updates your user PATH.

Build from source

Use a source build when contributing to Presolve itself or when you intentionally need an unreleased commit:

git clone https://github.com/fierstdev/presolve.git
cd presolve
cargo build -p presolve-cli
./target/debug/presolve --version

This is a contributor/development path, not the normal installation path.

Describe what is available here.

presolve env init
presolve env provider add memory-services --provides kv,objects
presolve env show
presolve env check

The environment tooling generates and persists stable environment/provider identities so normal local development does not require hand-managing opaque IDs. env show explains the discovered environment; env check validates the environment declaration itself.

Five commands, five different jobs.

presolve inspect
presolve inspect --json

presolve build
presolve inspect dist/orders.presolved

presolve check
presolve check dist/orders.presolved --json

presolve plan
presolve plan dist/orders.presolved --json

presolve dev
presolve dev --input "hello"

Inspect the decision before runtime objects exist.

A deployment plan is the recorded result of matching one application to one environment. It identifies what Presolve selected; it does not contain live database clients, sockets, secrets, or cloud SDK objects.

application: orders 1.0.0
environment: production
status: resolved

presolve:sql/database
  provider: postgres-sql
  version: 0.1.0
  features: dialect-postgresql, returning

presolve:objects/store
  provider: s3-objects
  version: 0.1.0
  features: range-read

The exact human formatting may evolve during preview. Automation should use the JSON form described below.

Use the versioned JSON projection for tooling.

presolve inspect --json
presolve check --json
presolve plan --json
presolve inspect dist/orders.presolved --json

Every machine payload identifies the explicit CLI schema rather than directly serializing internal Rust structs:

{
  "schema": "presolve.cli",
  "schema_version": "0.1",
  "kind": "..."
}

Rejected check and plan calls write their structured payload to stdout and return a non-zero status. Branch on stable problem type/code fields rather than scraping human text.

Stable codes separate application errors from compatibility failures.

Application validation can return multiple PS1xxx diagnostics. Compatibility failures preserve PS2xxx codes through check, plan, and local execution.

{
  "status": "rejected",
  "plan": null,
  "problems": [
    {
      "type": "missing_capability",
      "code": "PS2001",
      "interface": "presolve:kv/store",
      "version": "^0.1"
    }
  ]
}

presolve dev closes the local loop.

The local path discovers the application and environment, validates compatibility, constructs the plan, materializes supported local provider/runtime configuration, and executes through the same architecture used by detached-release checkpoints.

presolve env check
presolve check
presolve plan
presolve dev

dev is convenient for local iteration; check and plan remain useful separately because they let you inspect compatibility and decisions without executing anything.

Run the portability claims directly.

See the detailed proof walkthroughs →

Follow the command into the concept.