I Built the Universal Run Button for Every Project on My Machine

The author built Axiom to replace the typical triad of commands—`npm install && npm run dev`, `pip install -r requirements.txt && python main.py`, and `cargo run`—with a unified interface. By scanning for signature files such as `package.json`, `requirements.txt`/`pyproject.toml`, and `Cargo.toml`, the tool classifies the project and hands off execution to a language‑specific provider that knows how to install runtimes, resolve dependencies, and launch the entry point. Rust was chosen for its speed, static binary output, and strong type safety, which helped catch orchestration bugs early. The architecture separates detection, a provider abstraction layer, and an execution orchestrator, while a dependency‑graph model and a local cache under `~/.axiom/cache` aim to make repeated runs faster and enable future parallelism or incremental builds.

The problem Axiom tackles—fragmented developer workflows across Node, Python, and Rust—is a long‑standing pain point that has spurred a niche of “universal” tooling, from language‑agnostic task runners like `make` or `just` to environment managers such as `direnv` and container‑based solutions like Docker. Axiom differentiates itself by staying lightweight (a single static binary) and by embedding a provider plug‑in system that could be extended to Go, Java, or even niche runtimes. Its focus on a dependency graph and cache hints at ambitions beyond simple “run” commands, potentially positioning it as a competitor to more heavyweight build orchestrators (e.g., Bazel) that also aim to reduce redundant work across heterogeneous codebases.

Looking ahead, Axiom’s success hinges on how well it can keep pace with the evolving conventions of each ecosystem—new package managers (e.g., `pnpm`, `poetry`), custom startup scripts, or monorepo layouts could break its detection heuristics. Cache invalidation remains a technical risk; stale metadata could lead to silent failures or unnecessary rebuilds. The roadmap mentions AI‑assisted project analysis, which could improve detection accuracy but also adds complexity and data‑privacy considerations. Adoption will likely start among developers who frequently switch between small to medium projects, while larger teams may demand tighter integration with CI pipelines and enterprise security policies.