CLI Platform and Developer Experience
A terminal-native client for automation and serious workflows.
“The best tools disappear into the developer workflow.”
A first-class CLI, not a thin wrapper
The terminal remains the common language of professional software engineering because it is scriptable, reproducible, fast, composable, and independent of graphical interfaces. If AlgoLens wants to become a standard, it must exist naturally in that environment instead of treating the CLI as a small HTTP wrapper around the API.
The CLI should support local execution for offline speed, remote execution for heavy workloads, and hybrid execution that chooses intelligently. It should expose coherent command families inspired by Git: run, trace, explain, export, share, compare, benchmark, profile, login, sync, project, cache, apikey, billing, and organization. Internally, commands become action graphs that can be validated, compiled, instrumented, executed, traced, analyzed, and rendered.
Developer experience matters. The CLI should produce intelligent terminal output, JSON for machines, SVG/GIF/PDF/HTML exports for humans, shell completions for Bash, Zsh, Fish, and PowerShell, global configuration, local caching, plugin commands, observable internal timings, and CI-friendly exit codes.
algolens trace quicksort.js ↓ Validate ↓ Parse ↓ Instrument ↓ Sandbox Execute ↓ Trace ↓ Semantic Analysis ↓ Terminal Output · JSON · SVG · GIF · PDF