DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to move an existing CadQuery script into SOMA with SOMA

Open a CadQuery script in SOMA, let the agent extend it, and export it back as a script.

Credentials. The agent runs in a terminal on your machine with the login you set up, so review its commands and permission settings before letting it change files.

Who it is forA developer with an existing CadQuery script who wants agent help and a 3D viewer in one place.

The problemCadQuery scripts are hard to review and change visually, and extending them by hand is slow.

The outcomeA SOMA model built from your script, with agent-made changes, that can be exported back as a CadQuery script.

What you need first

  • Windows, Linux, or macOS (Apple Silicon) with a SOMA package downloaded from somacad.app/download or the releases page
  • A CLI agent such as Claude Code, OpenCode, Codex CLI or Gemini CLI, installed and logged in by you
  • About 1 GB of free disk space for the installed app

Steps

  1. Install SOMA and start it.
  2. Start your agent with the + above the terminal, then ask it to load your existing CadQuery script into a SOMA model.
  3. Ask the agent to make the changes you need and check the result in the 3D view.
  4. Export the model from the menu as a script for CQ-editor or VS Code.

Prompt for your agent

In the SOMA model folder for <model name>, import the CadQuery script at <script path> into the model, make the change <change description>, run `soma build`, and report whether the build succeeds. Verify that the exported script still produces the same part geometry.

Caveat. The README says the exported script includes compatibility code under Apache 2.0, so check the license terms before sharing the exported script.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page