Skip to content

cli

The single dbx (alias dbx-tools) commander entry.

One bin, three command groups:

  • dev - workspace lifecycle: detect the root, bootstrap or repair, then forward whatever follows to projen. This is the passthrough, and it is an EXPLICIT subcommand rather than the bare root action so a projen task name can never shadow (or be shadowed by) a sibling command.
  • model-proxy - the local OpenAI-compatible Model Serving proxy.
  • appkit - AppKit environment helpers (appkit env).

The two feature groups stay in their own packages (@dbx-tools/cli-model-proxy, @dbx-tools/cli-appkit-env) and are await import()ed only once their name is matched, so dbx dev never loads the Databricks SDK or AppKit. That lazy hop is also why they are mounted as ARG-FORWARDING commands instead of addCommand(): building a child program eagerly to register it would defeat the point. Each forwards its own --help, so the child prints its real help.