Using the CLI#
JITX can be driven entirely from the command line through the jitx command.
The CLI interface allows you to perform all the standard interactions:
installing and updating the JITX runtime
scaffolding a new project
managing project dependencies
discovering and building designs
collecting diagnostics and filing support tickets
Additionally, you can use the CLI to open the interactive board and schematic editors, where you can place and route components by hand. This makes the CLI a good fit for terminal-centric workflows, headless and CI environments, and designing circuit boards in collaboration with coding agents like Claude Code.
The VSCode extension invokes the CLI internally. This means you can manage the same project either from the CLI or via VSCode. You can also share the same project between collaborators using either or both workflows.
Warning
Collaborators on a shared project should be on the same JITX runtime version.
The runtime is installed separately from the project’s Python dependencies, so mismatched versions can produce different build results.
Check what’s currently installed with jitx runtime introspect.
Tip
The cleanest way to keep everyone in step is to pin your jitx version in pyproject.toml.
The 4.4.0 scaffold ships jitx>=4.4.0,<5; tighten it to jitx==4.4.0 for reproducible builds, or jitx>=4.4.0,<4.5 for updates within the 4.4 series. Align the standard library dependency too.
With jitx pinned, running jitx runtime install from inside the project installs the matching runtime for every collaborator — no --version needed.
Using the CLI
The command reference covers all public JITX 4.4.0 commands and options, including authentication, support, exports, and runtime maintenance. Older scripts may use jitx find, jitx build, or jitx build-all; these remain compatibility aliases for jitx design find, jitx design build, and jitx design build --all.