Chudware

Chudware is open-source parametric CAD for engineers. Its native C++ application uses Open CASCADE Technology for B-rep geometry and keeps parts in a human-editable feature history. Build with constrained sketches and features, then revisit the relations and dimensions that define the design.

Agent-assisted modeling brings a team of agents together across the workspace to work on engineering tasks and create editable histories, using geometric relations and critical dimensions rather than treating the result as a disposable mesh. You can also work directly in the desktop interface or connect an external agent through MCP.

Website: https://chudware.com · Development history

The animation is a sequence of real captured modeling steps, not a continuous recording.

What is here

Chudware brings several engineering workflows into one project:

• Parametric parts, assemblies and drawings, with a native .step+ document and build-dependent import/export options.
• Manufacturing tools including CAM, and an electronics project hub using KiCad 10 for schematic/PCB editing, checks and fabrication output; agents edit through ECAD operations.
• Simulation and design tools, including structural FEA, fluid flow, piping networks and industrial sizing. The generated simulation, piping and industrial guides describe individual workflows and their limits.

Availability depends on the build, platform, format, solver and installed external tools; the browser image does not provide full desktop parity. An available command or an example is not proof that a result is suitable for a particular engineering decision. Check its assumptions, convergence and applicable evidence. The format reference distinguishes implemented capabilities from reference and planned work.

Project status

Chudware is under active development and has not reached 1.0. File formats and APIs can change. Existing GitHub releases are prereleases; there is no current public stable desktop installer or stable /releases/latest installation path. Build from source or use the experimental self-hosted browser deployment below.

The optional owner-operated paid hosting offering supports the open-source project and covers operation and convenience; it does not unlock software features. There is no public checkout or promise of current availability. Contact the project for hosting inquiries.

Start in your browser

The experimental Compose deployment is for one trusted operator on a Linux x86-64 host. Anyone who can reach the gateway controls that operator's workspace; it is not a multi-user service. Online Copilot is unavailable in this deployment.

The default image uses the moving edge development channel. If the image has been published and made accessible, start it with:

git clone --depth 1 https://github.com/Hunter-124/Chudware.git
cd Chudware
docker compose -f web/compose.yaml up --pull always --no-build -d --wait

Open http://127.0.0.1:8300/app/. You need Git, Docker Engine with Compose v2 2.24.4 or newer, and nested unprivileged user namespaces. Ubuntu 24.04+ may require the AppArmor host setup before starting Compose. A current browser with WebAssembly, WebGL2 and cross-origin-isolated shared memory is required. The shallow clone can be replaced with a full clone by omitting --depth 1.

See the web deployment guide for source builds, image pinning, the trust boundary, persistence, backups, authenticated HTTPS and feature limitations. A source build is an alternative when the image is unavailable.

Building from source

The desktop build needs a C++20 toolchain, CMake 3.24+, Ninja, OCCT 7.9.x, Python 3.13 (3.12 also works) and Git. Linux also needs the X11/Wayland/OpenGL and libcurl development libraries; other native dependencies are fetched at pinned versions. Internet access is needed for the source dependencies and Python packages. The optional online-agent SDK is installed by the development Python provisioning step; its executable is obtained separately. Install KiCad 10 separately for electronics editing, checks and exports; it is a recommended companion application and is not bundled with Chudware.

For a Fedora Linux source checkout, the following configures the OCCT engine tree consumed by the GUI and builds the app without the optional embedded CEF browser backend:

git clone https://github.com/Hunter-124/Chudware.git
cd Chudware
sudo .github/scripts/install-fedora-deps.sh
PYTHON=python3.13 scripts/provision_venv.sh pytest
cmake -S core -B core/build-occt-linux -G Ninja \
    -DCMAKE_BUILD_TYPE=Release -DCHUDWARE_WITH_OCCT=ON
cmake -S host -B host/build-linux -G Ninja \
    -DCMAKE_BUILD_TYPE=Release -DCHUDWARE_ENABLE_CEF=OFF
./build.sh all

Set CMAKE_BUILD_PARALLEL_LEVEL=1 before ./build.sh all to keep native builds single-job on memory-constrained machines.

The provisioning script creates .venv-mcp, installs requirements.txt including the hash-pinned official OMP SDK source, and audits runtime dependencies. To enable CEF, obtain its SDK with scripts/fetch_cef_posix.sh and configure the host accordingly. Linux and macOS use system OCCT; on Windows CMake provisions its pinned OCCT SDK. See the Windows build guide, CMake presets and build.sh for other targets and build modes. macOS uses host/build-macos-<arch>/.

This is the beginning of the README. Read the rest at the original. Read the full README ↗