# AI use cases for Partmode (BOMWiki/partmode) Repo: [BOMWiki/partmode](https://github.com/BOMWiki/partmode) | Use cases: 4 | Page: https://dedupedai.com/use-cases/bomwiki-partmode/ PartMode is an open-source, browser-based parametric 3D CAD application built on OpenCascade WebAssembly, with typed, permissioned agent access to the same document model. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Model a parametric part in a local PartMode browser: https://dedupedai.com/use-cases/bomwiki-partmode/model-a-part-in-local-partmode/ - Let an approved MCP agent revise an open CAD project: https://dedupedai.com/use-cases/bomwiki-partmode/let-an-agent-edit-an-open-project/ - Run unattended CAD edits on a durable headless project: https://dedupedai.com/use-cases/bomwiki-partmode/run-unattended-cad-on-a-headless-server/ - Ship a PartMode CAD fix that passes the contributor gate: https://dedupedai.com/use-cases/bomwiki-partmode/contribute-a-cad-fix-with-the-release-checks/ ## How to model a parametric part in a local PartMode browser with Partmode Repo: [BOMWiki/partmode](https://github.com/BOMWiki/partmode) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Run PartMode on your own machine and build a constrained, editable 3D part in the browser. **Who it is for:** A mechanical designer or hobbyist who needs CAD without installing desktop software and does not want an account. **The problem:** Desktop CAD installs are heavy, and cloud CAD often requires sign-in before any modeling starts. **The outcome:** A running local PartMode instance where the user has modeled a parametric part with constrained sketches and feature history. ### Steps 1. Run `git clone https://github.com/BOMWiki/partmode.git` and then `cd partmode`. 2. Run `npm ci`, then `npm run build`. 3. Run `npm start`. 4. Open `http://127.0.0.1:4401` in a browser and open an editable template. 5. Edit a dimension, then confirm the rebuilt geometry and export STEP from the interface. ### Prompt to paste into your agent ```text In the BOMWiki/partmode repository, follow the local run steps in the README to start PartMode on http://127.0.0.1:4401, then report the URL that responds and the name of the template you opened. Verify that the server prints no build errors before reporting success. ``` ### Caveat PartMode is engineering software and not a certification authority, so dimensions and materials must be validated before any manufacturing use. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bomwiki-partmode/model-a-part-in-local-partmode/ ## How to let an approved MCP agent revise an open CAD project with Partmode Repo: [BOMWiki/partmode](https://github.com/BOMWiki/partmode) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Connect Codex to PartMode so the agent works on your open project after you approve it in the browser. **Who it is for:** An engineer who wants an AI coding agent to propose and commit CAD changes while staying in control of approval. **The problem:** Agents editing CAD through opaque scripts are hard to review, and giving an agent direct access to a model is risky. **The outcome:** A browser-approved agent session where the agent inspects the current state, previews a change, and commits it against the matching revision. ### Steps 1. Create a revocable key from Agent access at https://partmode.com/account and store it in the secret environment for your MCP client, not in a prompt or repository file. 2. Run `codex mcp add partmode --url https://partmode.com/mcp --bearer-token-env-var PARTMODE_AGENT_KEY`. (inferred, check the README) 3. Start a new Codex session, read the PartMode Help resources, and call `cad_capabilities` before building a transaction. 4. Sign in to PartMode in a browser tab and approve the project-scoped agent session when prompted. 5. Review the detached preview in the browser, then accept or reject the commit, and revoke the key when finished. ### Prompt to paste into your agent ```text Using the PartMode MCP server configured for this repository, call cad_capabilities, then inspect the open project at and create a detached preview of the change . Report the operations you proposed and the document revision they target, and verify that no commit happens until the person approves it in the browser. ``` ### Caveat Browser-approved sessions use a relay that is not end-to-end encrypted, and the browser project itself is not stored on the relay. Risk, credentials: The agent key authenticates the agent, so store it only in the secret environment for your MCP client and revoke it when access is no longer needed. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bomwiki-partmode/let-an-agent-edit-an-open-project/ ## How to run unattended CAD edits on a durable headless project with Partmode Repo: [BOMWiki/partmode](https://github.com/BOMWiki/partmode) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Create an explicit headless edit key so an agent can revise a server-stored project without a browser. **Who it is for:** A developer automating a repeatable parametric part family who needs an agent to commit changes with no person watching. **The problem:** Browser approval blocks unattended batch work, so the project needs a server-side document with its own authority. **The outcome:** A committed headless document that persists across session expiry and restarts, plus a STEP export produced by the headless path. ### Steps 1. Create an edit key from Agent access at https://partmode.com/account with an explicit, immutable headless grant. 2. Store the key in the secret environment for your MCP client and connect it with `codex mcp add partmode --url https://partmode.com/mcp --bearer-token-env-var PARTMODE_AGENT_KEY`. (inferred, check the README) 3. Call `cad_capabilities` at the start of each session and use the headless STEP workflow for export. 4. Commit changes only against the current document revision, and confirm each committed record in the account. 5. Plan account deletion as the only way to remove committed headless records, since there is no individual project-delete control yet. ### Prompt to paste into your agent ```text Using the headless PartMode edit key in the secret environment, call cad_capabilities, apply the change to the server project , and export the result as STEP. Report the committed revision and the STEP artifact name, and verify that the revision number increased by one after the commit. ``` ### Caveat Live headless sessions are key-bound, expire within one hour, and do not survive a service restart, so only committed documents persist. Risk, credentials: A headless edit key can change a durable server project without a browser approval step, so keep it secret and revoke it as soon as it is no longer needed. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bomwiki-partmode/run-unattended-cad-on-a-headless-server/ ## How to ship a PartMode CAD fix that passes the contributor gate with Partmode Repo: [BOMWiki/partmode](https://github.com/BOMWiki/partmode) | Difficulty: Advanced | Time: 2 hours | Basis: From the README Run the focused gate and the affected smoke checks before submitting a behavior change. **Who it is for:** An open-source contributor who has been assigned an issue on a CAD feature, assembly, drawing, or agent path. **The problem:** CAD changes need exact kernel evidence, not screenshots alone, so a fix needs the right regression checks before it is reviewed. **The outcome:** A pull request backed by a passing `npm run ci:gate` and the named smoke checks, with the settled document result reported. ### Steps 1. Comment on the GitHub issue before starting so scope and ownership are clear. 2. Run `npm ci`, then `npm run build`, and add or update the narrowest relevant regression. 3. Run `npm run ci:gate`. 4. Run each affected `smoke:*` command named by the issue, such as `smoke:brep-evidence` for exact geometry changes. 5. Report the settled document result and the kernel, B-rep, topology, or export evidence in the pull request. ### Prompt to paste into your agent ```text In the BOMWiki/partmode repository, make the change described in issue within its accepted boundary, run `npm run ci:gate`, and run the affected smoke checks listed in the issue. Report the gate result and the exact kernel or export evidence, and verify that the gate exits with status 0 before opening a pull request. ``` ### Caveat Screenshots and mesh counts are only supporting evidence, so the pull request must report exact kernel, B-rep, topology, or export results. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bomwiki-partmode/contribute-a-cad-fix-with-the-release-checks/