Documentation Index
Fetch the complete documentation index at: https://mintlify.com/dallay/corvus/llms.txt
Use this file to discover all available pages before exploring further.
Installation
Corvus can be installed in multiple ways depending on your platform and preferences. Choose the method that works best for your workflow.Corvus ships as a single self-contained binary (3.4MB) with no external dependencies. All installation methods provide the same functionality.
Prerequisites
Before installing Corvus, ensure you have the following prerequisites for your chosen installation method:- npm/pnpm/yarn/bun
- Cargo (Rust)
- Binary Download
Node.js 18+ (for package manager installation)Check your Node.js version:If you need to install or update Node.js, visit nodejs.org.
Installation Methods
NPM Package Manager (Recommended)
The fastest way to get started with Corvus is via npm, pnpm, yarn, or bun. The package automatically downloads and manages the appropriate Rust binary for your platform.Platform-specific binaries
Platform-specific binaries
The npm package includes optional dependencies for each platform:
@dallay/corvus-darwin-x64(macOS Intel)@dallay/corvus-darwin-arm64(macOS Apple Silicon)@dallay/corvus-linux-x64(Linux x64)@dallay/corvus-linux-arm64(Linux ARM64)@dallay/corvus-windows-x64(Windows x64)
- No Rust toolchain required
- Automatic platform detection
- Easy updates via package manager
- Works with npx/pnpm dlx/yarn dlx/bunx without installation
- Requires Node.js 18+
- Slightly larger download (includes npm wrapper)
Build from Source with Cargo
For maximum control and the latest development version, build Corvus from source using Cargo.Build Release Binary
- Release:
target/release/corvus - Debug:
target/debug/corvus - Dist profile:
target/dist/corvus
Install Globally (Optional)
Install the binary to your system:This installs to
~/.cargo/bin/corvus (ensure this is in your PATH).Build profiles explained
Build profiles explained
Corvus uses multiple Cargo profiles for different use cases:
The default
| Profile | Optimization | LTO | Codegen Units | Use Case |
|---|---|---|---|---|
| release | -Oz (size) | thin | 1 | Standard distribution |
| release-fast | -Oz | thin | 8 | Fast builds on powerful machines (16GB+ RAM) |
| dist | -Oz | fat | 1 | Maximum size optimization for distribution |
| dev | -O0 | none | 256 | Fast compilation during development |
release profile uses codegen-units = 1 for low-memory devices like Raspberry Pi 3.- Latest development features
- Maximum performance
- Full control over build flags and features
- No intermediate wrapper layers
- Requires Rust toolchain (1.75+)
- Longer build time (2-5 minutes on first build)
- Must manually update via git pull
Binary Download
Download pre-built binaries directly from GitHub Releases.Download for Your Platform
Visit the Corvus Releases page and download the appropriate binary:
- macOS (Intel):
corvus-darwin-x64 - macOS (Apple Silicon):
corvus-darwin-arm64 - Linux (x64):
corvus-linux-x64 - Linux (ARM64):
corvus-linux-arm64 - Windows (x64):
corvus-windows-x64.exe
- No toolchain dependencies
- Instant setup
- Smallest download size (3.4MB)
- Manual download and PATH setup
- Manual updates required
Optional Dependencies
Corvus supports additional features via optional dependencies:Docker (for Sandboxing)
To use Docker-based sandboxing for secure command execution:~/.corvus/config.toml
SurrealDB (for Advanced Memory)
To use SurrealDB as the memory backend:~/.corvus/config.toml
Platform-Specific Notes
macOS
Apple Silicon (M1/M2/M3)
Apple Silicon (M1/M2/M3)
Use the
corvus-darwin-arm64 binary. If you see Rosetta 2 warnings, ensure you downloaded the ARM64 version, not x64.Gatekeeper warnings
Gatekeeper warnings
On first run, macOS may block the binary with a security warning:
- Open System Preferences → Security & Privacy
- Click “Allow Anyway” next to the Corvus message
- Re-run the command
Linux
Permission denied
Permission denied
Ensure the binary is executable:
GLIBC version errors
GLIBC version errors
Corvus is statically linked with musl for maximum compatibility. If you encounter GLIBC errors, ensure you’re using the correct binary for your architecture (x64 vs ARM64).
systemd service (persistent daemon)
systemd service (persistent daemon)
To run Corvus as a systemd service:This creates a user service that survives logout and reboot.
Windows
Windows Defender warnings
Windows Defender warnings
Windows Defender may flag the binary as unrecognized. Add an exception:
- Open Windows Security → Virus & threat protection
- Click Manage settings → Add or remove exclusions
- Add the Corvus binary path
PowerShell execution policy
PowerShell execution policy
If scripts fail to run, update your execution policy:
Verification
After installation, verify that Corvus is working correctly:Measure Binary Size and Startup Time
- Binary size: ~3.4MB
- Startup time: <10ms on modern hardware
Updating Corvus
NPM Installation
Cargo Installation
Binary Download
- Download the latest release from GitHub Releases
- Replace your existing binary
- Restart any running Corvus services:
Corvus checks for updates automatically when you run
agent, daemon, or status commands. Set CORVUS_DISABLE_UPDATE_CHECK=1 to disable update notifications.Next Steps
Quickstart
Complete the onboarding wizard and run your first agent
Configuration
Learn about all configuration options
Development
Set up your development environment
API Reference
Explore the complete API documentation
Troubleshooting
Installation fails with npm
Installation fails with npm
- Clear npm cache:
npm cache clean --force - Check Node.js version:
node --version(requires 18+) - Try with verbose logging:
npm install -g @dallay/corvus --verbose - Fall back to binary download or Cargo installation
Cargo build fails
Cargo build fails
Common causes:
- Outdated Rust: Update with
rustup update - Low memory: Use
cargo build --profile releaseinstead of--profile dist - Missing system dependencies: Install build-essential (Linux) or Xcode Command Line Tools (macOS)
Binary not executable
Binary not executable
macOS/Linux:Windows:
Ensure you’re running PowerShell or Command Prompt as Administrator if moving to System32.
Command not found after installation
Command not found after installation
Ensure the installation directory is in your PATH:npm/pnpm/yarn/bun:Cargo:Add to PATH if missing:
Still having issues? Check the GitHub Issues or join the community discussions.