algovis/ lab

At home in your terminal

Your code.
Your machine.
A clearer answer.

The same native complexity analyzer, one command away. Keep your workflow, keep your code local.

Get the CLI ↓Read the docs →
TERMINAL / ~/solutions$ algovis analyze solution.cpp
Time: O(n * log n)
Space: O(n)
Illustrative output · no server connection needed

Meet your new command.

Choose a prebuilt binary or build the analyzer from source. No account is needed.

Up and running.

On an Apple Silicon Mac, download both the archive and its checksum, then open Terminal. These commands assume both files are in Downloads.

1. Verify the archive

Terminal 
cd ~/Downloads
shasum -a 256 -c algovis-macos-apple-silicon.tar.gz.sha256

The result should end with OK. Continue only if verification succeeds.

2. Install in your user folder

Terminal 
tar -xzf algovis-macos-apple-silicon.tar.gz
mkdir -p ~/.local/bin
cp algovis-macos-apple-silicon/algovis ~/.local/bin/algovis
chmod +x ~/.local/bin/algovis
export PATH="$HOME/.local/bin:$PATH"
algovis --help

No administrator password is needed. To keep this command available in new zsh terminals, add export PATH="$HOME/.local/bin:$PATH" once to your ~/.zprofile.

3. Analyze a solution

Terminal 
algovis analyze ~/Downloads/solution.cpp

To update, download and verify the new archive, then repeat the install commands. They replace the binary in ~/.local/bin.

The answer. Or the whole story.

Choose a compact time and space summary, or inspect the full report with detected patterns, signals, and rough constraints.

Notation · the default

Summary 
algovis analyze solution.cpp
algovis analyze notation solution.cpp
algovis analyze solution.cpp --notation

Full · the reasoning

Report 
algovis analyze full solution.cpp
algovis analyze solution.cpp --full
algovis --help

Supported extensions: .cpp, .cc, .cxx, .hpp, .hh, and .hxx. Quote paths that contain spaces. A bare file name also checks Downloads, Desktop, and Documents if it is not in your current folder.

Make it your own.

The analyzer is open source. Install a C++17 compiler, make, and SQLite development headers using your system's tools, then build locally.

Build from source 
git clone https://github.com/daiseikai/algovis.git
cd algovis
make
./algovis analyze path/to/solution.cpp

See the repository README ↗ for platform-specific requirements and the development workflow.

A little help along the way.

macOS says the developer cannot be verified

The binary is unsigned. After verifying the checksum, use System Settings → Privacy & Security to allow the downloaded Algovis binary, then retry. Only do this for a download you trust.

Terminal says “command not found”

Check that ~/.local/bin/algovis exists. Run export PATH="$HOME/.local/bin:$PATH" for this terminal, or invoke the full path: ~/.local/bin/algovis --help.

The estimate is different from what I expected

Algovis uses pattern-based heuristics, not a formal proof. Use --full to inspect the signals. Custom types, unusual control flow, and incomplete snippets can need manual reasoning.

Does my source code leave my machine?

The CLI analyzes files locally. It does not send source code to the hosted analyzer. In the web app, the analyzer sends code to the Algovis server, while the playground compiles in your browser.