Codevisor DocsInstallation
Install Codevisor Server and its command-line tools on macOS or Linux.
Installer behavior
curl -fsSL https://www.codevisor.dev/install.sh | shOn Linux, the installer downloads the matching linux-x64 or linux-arm64 archive, verifies its
SHA-256 checksum when sha256sum is available, and links codevisor, codevisor-server, and
codevisor-terminal-proxy into a bin directory.
On macOS, the installer copies the Codevisor app into /Applications and links the same CLI
commands from the bundled server runtime into ~/.local/bin (override with CODEVISOR_BIN_DIR).
The Homebrew cask links them into Homebrew's bin directory, and the app also repairs the
~/.local/bin links on launch — so a plain DMG drag-install gets the CLI the first time the app
opens. If ~/.local/bin is not on your PATH, add it in your shell profile:
export PATH="$HOME/.local/bin:$PATH"| Variable | Purpose | Default |
|---|---|---|
CODEVISOR_VERSION | Install a specific release | Latest stable |
CODEVISOR_INSTALL_DIR | Runtime installation directory | ~/.codevisor/server or /opt/codevisor |
CODEVISOR_BIN_DIR | Command symlink directory | ~/.local/bin (/usr/local/bin as root, Linux) |
CODEVISOR_PORT | Listening port | 49361 |
CODEVISOR_DATA_DIR | Linux database and data dir | ~/.codevisor/data or /var/lib/codevisor/data |
CODEVISOR_NO_SERVICE=1 | Skip systemd setup | systemd enabled when available |
CODEVISOR_NO_SETUP=1 | Skip interactive onboarding | setup runs when a terminal is available |
Without systemd
CODEVISOR_NO_SERVICE=1 curl -fsSL https://www.codevisor.dev/install.sh | sh
codevisor startcodevisor start runs a detached background process when no systemd unit exists. Use
codevisor stop, codevisor restart, codevisor status, and codevisor logs --follow to manage it.
Run codevisor setup after the first start.
To use another supervisor, run the foreground command and give the service user a persistent home directory:
codevisor-server serve --host 0.0.0.0 --port 49361 --auth tokenUser service persistence
A systemd user service normally stops after its user logs out. Enable lingering if this machine should remain available:
sudo loginctl enable-linger "$USER"