Skip to content

Capability Map

This page lists the major capabilities bijux-cli currently provides and maps those capabilities to concrete source areas.

Visual Summary

flowchart TB
    runtime["Runtime capabilities"] --> parse["command parsing and normalization"]
    runtime --> routes["route resolution and alias rewrites"]
    runtime --> handlers["config, plugins, history, memory handlers"]
    runtime --> output["structured output and error shaping"]
    runtime --> diagnostics["status, doctor, audit diagnostics"]

Capability Inventory

  • Parse argv and normalize command intent
  • Resolve route ownership among built-ins, aliases, and plugins
  • Execute built-in handlers for runtime, config, memory, history, and plugin flows
  • Generate text, JSON, and YAML payloads with deterministic rendering policy
  • Emit usage/internal error classes with stable exit-code mapping
  • Run interactive REPL with shared command semantics

Code Anchors

  • crates/bijux-cli/src/routing/parser.rs
  • crates/bijux-cli/src/routing/model.rs
  • crates/bijux-cli/src/interface/cli/handlers/
  • crates/bijux-cli/src/interface/repl/
  • crates/bijux-cli/src/shared/output.rs
  • crates/bijux-cli/src/features/diagnostics/

Capability Edges

  • plugin execution is intentionally unsandboxed and trust-based
  • delegated known-tool routes preserve external tool output contracts
  • formatting options change rendering, not semantic contract meaning

Questions This Page Answers

  • what a user or automation script can expect from the current CLI runtime
  • which features are first-class capabilities versus implementation details
  • where to start code review for each major command domain

Next Reads