Workspace

The rx ws commands provide workspace-level orchestration for Cargo workspaces. Cargo commands run as a single --workspace invocation; shell commands run per member directory.

Listing members

rx ws list

Lists all workspace members with their paths and versions.

Dependency graph

rx ws graph

Displays the inter-package dependency graph of the workspace, showing which packages depend on which.

Running commands

rx ws run build                  # build all members
rx ws run test                   # test all members
rx ws run test --release         # test all members in release mode
rx ws run check                  # check all members

rx ws run <cmd> runs one cargo <cmd> --workspace from the workspace root. Cargo already builds independent crates in parallel — rx does not spawn one Cargo process per member.

Parallel waves

rx uses Kahn’s algorithm for topological sorting to group packages into parallel “waves”:

Wave 1: [core, utils]           # no inter-dependencies
Wave 2: [api, cli]              # depend on core/utils
Wave 3: [integration-tests]     # depends on api/cli

All packages in a wave run concurrently. The next wave starts only after the current wave completes.

Running shell commands

rx ws exec "wc -l src/*.rs"      # count lines in each member
rx ws exec "cargo doc"           # run arbitrary cargo commands
rx ws exec "echo \$PWD"         # show each member's directory

rx ws exec runs an arbitrary shell command in each member’s directory, in dependency order (topological sort).

Example workflow

A typical CI setup for a workspace:

# Check all members in dependency order
rx ws run check

# Test only affected packages
rx test --affected --base main

# Build everything
rx ws run build --release

Or use the rx ci command which handles the full pipeline automatically.

Cycle detection

rx detects dependency cycles in the workspace graph and reports them as errors. Cargo workspaces should not have cycles, but rx provides a clear error message if one is found.