简体中文

On this page

Installation

This page is the authoritative source for Sigil install channels, update and uninstall commands, and release-archive handling. Other user guides link here instead of copying those details. If you want a first-run walkthrough, start with Quickstart. Sigil remains an early preview, not a stable compatibility promise for config, plugins, advanced sandbox behavior, or automation surfaces.

The GitHub Pages documentation tracks main, so features listed under Unreleased may require a source install until the next beta is published. Exact versioned Cargo examples remain pinned to the most recent tagged source release.

Requirements

For Desktop: macOS on Apple Silicon or Intel.
For TUI: a modern terminal emulator.
One installer: a Desktop DMG, npm, Homebrew, or a Rust toolchain installed through rustup or an equivalent system package.
A model provider credential. Quick Setup can collect it on first launch.

Supported Install Channels

Channel	Current coverage	Use when
Desktop beta	Signed and Apple-notarized Apple Silicon and Intel DMGs published with the beta release.	You want a native conversation, approval, and settings workspace on macOS.
npm beta	Platform-specific optional binary packages behind `@sigil-ai/sigil@beta`.	You want the current public cross-platform TUI preview.
Homebrew tap	macOS formula in `JimmyDaddy/homebrew-sigil`, installed as `sigil-ai` while exposing the `sigil` command.	You manage terminal tools with Homebrew.
Cargo git tag	Builds from the tagged Git release with your local Rust toolchain.	You already use Rust tooling or need a source-based install.
GitHub release archive	Downloadable release archives with checksum files.	You need a manual or offline install.

Install Desktop On macOS

Open the GitHub prereleases page and download the DMG for your Mac:

Apple Silicon: Sigil_<version>_aarch64-apple-darwin.dmg
Intel: Sigil_<version>_x86_64-apple-darwin.dmg

Each beta release is published only after both DMGs, their SHA-256 files, and the signed update archives are present. The DMGs are Developer ID-signed, Apple-notarized, stapled, and verified before upload. Open the DMG, drag Sigil to Applications, then launch it normally.

Install TUI With npm

The npm package is scoped as @sigil-ai/sigil. It installs a small Node.js launcher plus a platform-specific optional binary package. The installed command is still sigil.

npm install -g @sigil-ai/sigil@beta

Confirm the install:

sigil --version
sigil doctor

The unscoped npm package name sigil is not the first-release package name.

Install With Homebrew

The Homebrew path uses a dedicated tap formula named sigil-ai to avoid confusing this project with other Homebrew software named Sigil. The formula installs the sigil binary.

brew install JimmyDaddy/sigil/sigil-ai

Confirm the install:

sigil --version
sigil doctor

The release workflow generates sigil-ai.rb from the macOS release archives. The formula is published in the JimmyDaddy/homebrew-sigil tap.

Install With Cargo

For the first release, Cargo installs from the Git tag rather than crates.io:

cargo install --git https://github.com/JimmyDaddy/sigil --tag v0.0.1-beta.4 --locked sigil

This installs the sigil binary into Cargo's binary directory. The default is ~/.cargo/bin on macOS and Linux, and %USERPROFILE%\.cargo\bin on Windows.

The crates.io package name sigil is already used by another package, so crates.io distribution needs a later package-name decision. The binary can still remain sigil.

Install From Source

If you prefer to build from a local checkout, run this from the repository root:

cargo install --path crates/sigil --locked

Confirm the install:

sigil --version
sigil doctor

Start

For normal use, open the repository or workspace you want Sigil to operate on and start the TUI there:

cd /path/to/workspace
sigil

If no usable config exists, Sigil opens Quick Setup. After setup, workspace.root = "." means the directory where you launched sigil is the active workspace.

Use explicit subcommands only for automation, diagnostics, or scripts:

sigil doctor
sigil run "summarize this repository"

Inside the TUI, /doctor renders the same diagnostics report in the transcript.

Install From A Release Archive

Use the package-manager paths above when possible. For a manual install, download the matching archive and checksum from the GitHub releases page, verify the checksum, unpack the archive, and place the sigil binary on your PATH.

The archive contains the sigil binary plus the user-facing README, logo assets, and installation docs. Desktop beta releases additionally carry signed updater archives; update installation remains an explicit user action.

Update

Use the installer you used originally:

npm install -g @sigil-ai/sigil@beta
brew upgrade sigil-ai
cargo install --git https://github.com/JimmyDaddy/sigil --tag v0.0.1-beta.4 --locked sigil --force
cargo install --path crates/sigil --locked --force

Desktop Settings can check the signed beta manifest, download and independently verify the architecture-matched update, and install it only after you choose Download and install. Restart is a separate action, and an active task blocks restart.

TUI and CLI can use:

sigil update check
sigil update apply --yes

The TUI equivalents are /update check, /update refresh, and /update apply. Add beta or stable after the action to opt into another channel, for example /update check beta; current follows the installed prerelease channel. Official standalone archives can be replaced only after checksum and release admission; npm, Homebrew, Cargo, and source installs instead show the owning installer command. Sigil does not silently install or restart an update in the background.

Uninstall

Use the matching uninstall command:

npm uninstall -g @sigil-ai/sigil
brew uninstall sigil-ai
cargo uninstall sigil

Remove Sigil.app from Applications to uninstall Desktop. Saved Sigil state is retained unless you remove it separately.

Next: Start with Quickstart.