INSTALLATION
Install the self-contained EveryCli v1.2.1 release without Rust, Cargo, Python, or a compiler. The bundle includes the CLI, daemon, model, tokenizer, native ONNX Runtime, corpus, and installer.
Linux x86_64 — one command
Run the installer from a normal Bash terminal. It downloads the latest Linux release, verifies its checksum, installs the binaries and model in your user directories, and configures the user-level systemd daemon.
$curl -fsSL https://raw.githubusercontent.com/HE11032006/EveryCli/main/install.sh | bash
Open a new terminal, or reload your profile with source ~/.profile, then verify the installation:
$source ~/.profile$everycli search "undo my last commit" --top 2 -i
Windows x86_64 — one command
Run the command from PowerShell. It downloads the latest Windows release, verifies the archive, installs the CLI and daemon in your user profile, and starts the user-level startup mode without requiring administrator rights.
$irm https://raw.githubusercontent.com/HE11032006/EveryCli/main/install.ps1 | iex
Open a new PowerShell window so the updated PATH is loaded, then run:
$everycli search "undo my last commit" --top 2 -i
The one-line mode deliberately uses the user-level startup path. If you explicitly want a Windows service with automatic restart, download the release archive, inspect the script, and run install.ps1 from a real local file with administrator elevation.
Requirements
End users need a 64-bit x86_64 Windows or Linux system, PowerShell or Bash, an HTTPS connection for the first download, and roughly 1 GB of free disk space for download and extraction. Rust, Cargo, Python, Node.js, and a compiler are not required. The first daemon start can take longer while the model is loaded and corpus embeddings are prepared; 4 GB of available RAM is a practical minimum and 8 GB is more comfortable.
Manual archive installation
If you prefer to inspect files before running them, download the Linux or Windows archive from GitHub Releases, verifySHA256SUMS, extract it, and run the matching installer included in the archive. This route is slower but more inspectable than the one-line command.
Uninstall
The uninstallers remove the installed binaries, links, PATH entries, and background startup mechanism. They preserve your personal configuration and commands by default. Run theuninstall.sh or uninstall.ps1 shipped with the release bundle; use the explicit data-removal option only when you also want to delete your personal corpus and configuration.
search path is local and does not need an API key.everycli ask is optional and needs an OpenAI-compatible API key only when you want an external model to propose a command that is not in the local corpus.