Skip to main content

rigbox

A manifest-driven REPL and CLI toolbox for embedded and DSP developers.

Setup

Requires Python 3.11 or newer.

python -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
.\.venv\Scripts\python.exe -m pytest -q
.\.venv\Scripts\ruff.exe check    # lint
.\.venv\Scripts\ty.exe check      # type check

Use

rigbox init my-project        # create a workspace (rigbox.yaml)
rigbox                        # interactive shell (run from inside a workspace)
rigbox run commands           # list the commands
rigbox run commands --help    # one command's arguments
rigbox run --format json commands
rigbox script workflows\x.yaml --var key=value

Output is a human message (or a table for data-only commands) on a terminal and NDJSON when piped. Select --format plaintext, rich, json, or ndjson explicitly when needed. Human formats fall back to available text or a table of structured data; plaintext output omits styling. JSON and NDJSON never fall back to human text: human-only results produce an explicit error. Empty results produce [] in JSON or no NDJSON records, without warnings.

The shell

The shell is a cmd2 app; every rigbox command is a shell command with the same arguments and --help as rigbox run. Tab completes command names, option names, choices and file names. cmd2's own commands work too:

rigbox> help                           # commands grouped by area; `help commands` or `commands --help` for one
rigbox> set format json                # print results as JSON (plaintext, rich, json, ndjson, auto)
rigbox> alias create list commands     # then: list
rigbox> commands | findstr workspace   # pipe to a shell command
rigbox> commands > commands.txt        # redirect to a file
rigbox> history                        # what you typed (kept in .rigbox/ inside a workspace)
rigbox> exit                           # or quit, or Ctrl-D

The bar under the prompt shows the workspace, open device connections and output format.

Plugins

See each plugin's README for commands, examples and behavior:

Layout

  • src/rigbox/core/: framework (registry, parsing, rendering, workspace, workflows, plugin loading)
  • src/rigbox/plugins/: built-in plugins
  • docs/decisions.md: architecture decisions and rationale
  • CLAUDE.md: conventions and preferences for contributors and Claude Code

Metadata

Release files for rigbox 1.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rigbox 1.0.2
File Size Uploaded
rigbox-1.0.2.tar.gz 89.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rigbox 1.0.2
File Interpreter ABI Platform
rigbox-1.0.2-py3-none-any.whl Python 3 none any Details

Total release size: 166.8 kB

Release files / rigbox-1.0.2.tar.gz

Download URL rigbox-1.0.2.tar.gz
Size 89.6 kB
Tags Source
SHA-256 checksum
How to use checksums
d7839913f7a2afd2eae6062312abf2729f657ebfe7c6bd448859b4b097ddec50
BLAKE2b-256 checksum
How to use checksums
67d02722ece06f31dcf3f08f0a1ef1d84afb14e5c5bc58a670b2ac5b77d938a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Release files / rigbox-1.0.2-py3-none-any.whl

Download URL rigbox-1.0.2-py3-none-any.whl
Size 77.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a8656d388e58da6b376f4652c9e222508ee2a72935e95d0107d799f178fde6e6
BLAKE2b-256 checksum
How to use checksums
43127f5ef9c9e71b7228406b894fa5fe69bf13235ef264ceadf8a8442317fa5b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.2 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page