Installation

Quick install

The command downloads a small bootstrap script from this repository. The bootstrap finds the latest release, downloads the installer for your system and processor, and checks it against the release's published SHA-256 checksums. Then it runs the installer. If the checksum doesn't match, it stops before running anything.

Prefer to read before running? Download installer/install.sh or installer/install.ps1, read it, then run it.

What the installer does

1. Checks, changing nothing. It looks for an existing mini-AlbertCode and its version, a running mini-AlbertCode service, a suitable Python, uv, Git, a browser for the browser tools, free disk space, and whether it can reach the package index.
2. Shows its plan and asks Proceed? [Y/N]. If you answer N, nothing changes.
3. Installs, for your user only.
   • It downloads what is missing first, so a failed download leaves an existing installation untouched.
   • It stops the service and replaces an older mini-AlbertCode, keeping your sessions.
   • It installs mini-AlbertCode in an environment of its own, so your other Python projects are unaffected.
   • It adds the albert-mini command to your PATH.
4. Verifies. It checks the version and the command. Then it starts the service once on a spare port, with a scratch folder of its own, and waits for it to answer with its version.

An example, on Linux:

mini-AlbertCode SWE Agent 0.1.11 installer
Checking this machine. Nothing is changed until you say so.

Found
  Linux            Ubuntu 24.04 LTS, x86_64
  mini-AlbertCode  not installed
  Python           3.12 at /usr/bin/python3.12
  uv               not installed
  Git              2.43.0 at /usr/bin/git
  Browser          /usr/bin/chromium
  Disk             26.9 GB free
  Network          pypi.org reachable

Will do
  1. Download uv 0.9.5 (about 20 MB, checked against its published SHA-256) ...
  2. Use your Python 3.12 (/usr/bin/python3.12); nothing is installed into it.
  3. Install mini-AlbertCode 0.1.11 with its browser tools, in its own environment ...
  4. Use /usr/bin/chromium for the browser tools (no browser download).
  5. Add ~/.local/bin to your PATH in your shell's startup file, so 'albert-mini' works in any new terminal.
  6. Check that it installed: its version, its commands, and its service starting and answering.

Proceed? [Y/N] Y

Installing
  ...
Checking the installation
  Version 0.1.11
  albert-mini starts
  Browser tools load
  Git works
  New terminals find albert-mini
  The service starts and answers (0.1.11)

mini-AlbertCode 0.1.11 is ready.
  Open a new terminal and run:   albert-mini
  Or open it in your browser:    albert-mini web
  Then connect a model: it asks on the first start, or /connect at any time.

Administrator rights are needed only if Git is missing: the installer uses winget on Windows, Apple's Command Line Tools on macOS, and your package manager (with sudo) on Linux.

Requirements

You don't need Python: the installer uses your Python 3.12 if you have one, and otherwise downloads one for mini-AlbertCode alone.

Options

Pass options to the bootstrap after -s -- on macOS and Linux:

curl -fsSL https://raw.githubusercontent.com/huynvic/mini-albertcode-swe-agent/main/installer/install.sh | sh -s -- --check

On Windows, set them in MINI_ALBERTCODE_INSTALL_ARGS before running the command:

$env:MINI_ALBERTCODE_INSTALL_ARGS = '--check'; irm https://raw.githubusercontent.com/huynvic/mini-albertcode-swe-agent/main/installer/install.ps1 | iex

Updating

albert-mini update            # find the latest release, and run its installer
albert-mini update --check    # only say whether there is a newer one

albert-mini update reads the latest release, says whether it is newer than the version you have, and runs its installer, checked against the release's SHA-256 first. Running the install command again does the same. The installer finds the version installed and shows its plan before replacing anything:

Found
  mini-AlbertCode  0.1.0 (uv, ~/.local/share/uv/tools/mini-albertcode/bin/python3)
  ...
Will do
  1. Update mini-AlbertCode 0.1.0 to 0.2.0 (installed with uv); your sessions are kept.
  ...
  5. Saved keys, model choices and settings are kept: it carries the same AlbertCode engine.
  6. Check that it installed: its version, its commands, and its service starting and answering.

Proceed? [Y/N]

Your sessions are always kept. When a new version carries a new AlbertCode engine, the plan says so, and saved keys and model choices are cleared the first time it starts: connect your model again with /connect. On Windows the installer opens in a window of its own, so it can replace the running program's files.

If a running mini-AlbertCode service is found, the installer stops it first (albert-mini stop does the same by hand); it starts again by itself the next time an interface needs it.

Uninstalling

albert-mini uninstall           # the program and the installer's files
albert-mini uninstall --all     # and your settings, saved keys, sessions and history
albert-mini uninstall --check   # only show what it would do

It shows its plan and asks Proceed? [Y/N] first. It needs nothing from the internet. The install script can do it too, keeping your settings:

curl -fsSL https://raw.githubusercontent.com/huynvic/mini-albertcode-swe-agent/main/installer/install.sh | sh -s -- --uninstall

$env:MINI_ALBERTCODE_INSTALL_ARGS = '--uninstall'; irm https://raw.githubusercontent.com/huynvic/mini-albertcode-swe-agent/main/installer/install.ps1 | iex

Your repositories are never touched. Your settings, sessions and saved keys stay unless you use --all; Privacy lists the folders.

Downloading an installer by hand

From the latest release, take the file for your system:

Check it against the release's SHA256SUMS before running it:

sha256sum -c SHA256SUMS --ignore-missing          # Linux
shasum -a 256 -c SHA256SUMS --ignore-missing      # macOS

(Get-FileHash .\Install-mini-AlbertCode-<version>-windows-x64.cmd -Algorithm SHA256).Hash   # Windows: compare with SHA256SUMS

The installers aren't code-signed yet. On macOS, the first time, choose Done, open System Settings → Privacy & Security, click Open Anyway, then open the installer again. On Windows, SmartScreen may say it protected your PC: choose More info → Run anyway. The one-line commands avoid both.

Behind a proxy

Set HTTPS_PROXY (and HTTP_PROXY) before running the command. The installer and mini-AlbertCode use it for every download. A network that inspects secure connections with its own certificate is handled too: the installer retries with your computer's own certificates.

Files and folders