Skip to content

What Bijux Is

Core Identity

bijux-cli is a command interface with Rust runtime ownership and Python distribution compatibility. The current system is centered on the Rust binary. The Python package is a supported way to install and invoke that runtime, not a second independent implementation.

flowchart LR
    A[User or automation] --> B[bijux binary]
    C[Python package] --> B
    D[REPL] --> B
    B --> E[Shared execution law]

This diagram shows the current entry surfaces that users actually touch. The important point is that they all terminate in the same runtime law instead of competing command implementations.

flowchart TD
    A[Current repository] --> B[Rust crates]
    A --> C[Python package]
    B --> D[Runtime ownership]
    C --> E[Packaging and compatibility]
    D --> F[Single command behavior model]
    E --> F

This second diagram explains the repository split. Rust crates own the runtime behavior, while the Python package keeps installation and compatibility duties without becoming a separate source of truth for command semantics.

What It Optimizes For

  • deterministic global flag behavior
  • explicit command and output contracts
  • plugin management and compatibility surfaces
  • machine-readable output for scripts and CI
  • one execution model shared by CLI and REPL

What It Is Not

  • not a general-purpose plugin sandbox
  • not a supported Windows host runtime
  • not a multi-runtime architecture where Python and Rust diverge by design
  • not a promise that every internal crate boundary is stable for downstream use

Honest Summary

Bijux is strongest when you want a command surface that stays scriptable as it grows. It is weaker if you need a fully sandboxed extension model or broad platform support today. The Rust runtime has gained some Windows-aware install and path handling, but the supported host contract still stops at Linux and macOS until the remaining POSIX-only product edges are removed.