bijux-cli¶
bijux-cli is the public Rust runtime behind the bijux executable. It is
the source of truth for command semantics shared by the native binary, the
Python launcher, and the in-process SDK surfaces used by mounted apps and
tests.
Use this page when the question is about what the bijux runtime actually
does: parsing commands, normalizing inputs, executing features, shaping
envelopes, and preserving deterministic behavior across entrypoints.
Reach For This Crate When¶
- the installed binary parses or renders something incorrectly
- a plugin, REPL flow, history path, config command, or runtime query behaves differently than expected
- a mounted app should use the same command semantics as the native runtime
- you need the stable Rust dependency that powers the visible
bijuxproduct
What It Owns¶
| Surface | Ownership |
|---|---|
| command routing | parser, registry, command catalog, and normalization |
| runtime behavior | config, history, memory, install diagnostics, plugins, and REPL state |
| output contract | deterministic help, envelopes, and stream formatting |
| boundary | does not own maintainer control-plane commands or DAG semantics |
What It Does Not Own¶
- Python packaging, interpreter discovery, and console-script distribution
rules belong to
bijux-cli-python. - DAG authoring and graph execution semantics belong to the
bijux-dag-*crates. - Repository governance, release proof, and maintainer diagnostics belong to the maintainer tooling surfaces.
Source Layout¶
crates/bijux-cli/src/apicrates/bijux-cli/src/bootstrapcrates/bijux-cli/src/contractscrates/bijux-cli/src/featurescrates/bijux-cli/src/infrastructurecrates/bijux-cli/src/interfacecrates/bijux-cli/src/kernelcrates/bijux-cli/src/routingcrates/bijux-cli/src/shared
Practical Starting Points¶
- Open the CLI Handbook when you need the product story before choosing a module.
- Open CLI Interfaces when the question is what callers can rely on.
- Open CLI Operations when the question is installation, diagnostics, release handling, or day-to-day runtime support.
- Open
bijux-cli-pythonwhen the issue is Python packaging, bridge parity, or launcher distribution.
Code Anchors¶
crates/bijux-cli/README.mdcrates/bijux-cli/CHANGELOG.mdcrates/bijux-cli/src/bincrates/bijux-cli/tests/integration.rscrates/bijux-cli/tests/routing.rs
Review Focus¶
- runtime semantics should stay deterministic across binary and bridge entrypoints
- public command behavior should be explained in the CLI handbook, not hidden in tests
- maintainer-only concerns should not leak into this package boundary