v0.6.4

What changed in this release: CHANGELOG.md

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.6.3

What changed in this release: CHANGELOG.md

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.6.2

What changed in this release: CHANGELOG.md

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.6.1

What changed in this release: CHANGELOG.md

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.6.0

What changed in this release: CHANGELOG.md

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.5.8

0.5.8 (2026-09-07)

• "This environment cannot import OCP or build123d" was sometimes a false alarm, and the advice under it made things worse. With cadquery in the environment, the startup check imported everything successfully and then faulted on the way out — Windows corrupts the heap while unloading the OpenCascade libraries — and only the exit code was read, so a run that had done its whole job was reported as an environment that could import nothing. The prompt then offered Restore, which would have replaced a perfectly good configuration, local checkouts and all. The check now leaves without a teardown, and says which half of it succeeded: trouble with cadquery — which you add yourself, and which the application never imports — is written to the log and stops nothing.

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.5.7

0.5.7 (2026-09-07)

• A window whose link to the application has died says so again, and keeps saying it. On Windows, waking from a long sleep breaks two connections at once: the one to the Python backend, which is redialled and comes back, and the one to the application itself, which cannot be. The second is the serious one — nothing can be saved, nothing logged, and the window cannot be closed — and the offer to reload, which is the only way out, was being wiped off the screen a second later by the backend's own recovery. What was left was a window that ran code perfectly, wrote nothing to its log, and could not be quit, with nothing on screen to explain it. Found on a machine that had been asleep for four days.

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.5.6

0.5.6 (2026-09-07)

• Run → Test File and Test Folder. Pick a file or a folder and pytest runs over it, in a process of its own — the report arrives in the Run/Debug tab and the Stop beside it ends the run, exactly as Run File works. pytest is part of the environment from this release on. Settings → Test carries one switch, Ignore warnings, which adds -W ignore for a suite where the same deprecation is raised a hundred times and buries the summary.
• Restart Kernel now sits above Run File in the Run menu. Everything above that line runs on the kernel and shares its namespace; everything below it runs in a process of its own and leaves nothing behind.
• About says how to reach the kernel from outside. The connection file has a section of its own at the foot of the dialog, with the jupyter-console --existing "…" command to attach to the running kernel — and the warning that matters: leave that console with Ctrl-D, because a typed exit shuts the kernel down.
• Every path in About has a copy button, and the values have the room the labels were wasting — the first column was sized as a share of the panel and spent 120 pixels on nothing. A path that wrapped over four lines and had to be selected by hand is now one click. The full package list moved to the very bottom, below everything anybody is meant to find by reading.
• About shows the OCP you actually have. It only ever listed cadquery-ocp-novtk, so an environment with the VTK build — which is most of them — read "not installed" and never showed a version at all. Both are listed now, and ocpsvg has left the short list.
• Opening a file gives it the keyboard. From the tree or from the menu, the file opened without a cursor in it: nothing is drawn while the editor does not have focus, so it looked ready to type into and was not.
• Dark mode moved to Settings → Application, with the other settings that are about the application rather than about one pane.
• The shipped dependency lock matches what the release declares again. The lock in 0.5.2 through 0.5.5 was the one resolved for 0.5.1: it predated both the OCP type stubs and the ocp-viewer-core floor those releases declared, so a fresh environment re-resolved over the network at its first start instead of beginning from the versions the release was tested with. The lock is now part of what a release commits, so it cannot fall behind again.
• A test run and a file run cannot collide. Only one child process at a time, as before — asking for a test run while something is running now says so, rather than starting nothing and explaining nothing.

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.5.5

0.5.5 (2026-09-03)

• The kernel indicator says how much is waiting. Pressing Run while a cell is running queues it, as in Jupyter — the indicator now reads busy [+1], busy [+2] and counts back down. Until now nothing said so: the indicator already read busy and the console shows In [n] only when a run actually starts.
• Interrupting no longer offers to restart a kernel that obeyed. Interrupt a cell, let it stop, run something else within five seconds, and "The kernel did not stop" appeared over a kernel that had stopped when asked. A second interrupt during that window also got no grace of its own.
• The keyboard goes back to the editor after a Run. Run Cell moves the caret to the next cell, and the cursor is not drawn while the editor does not have focus — so a run from the toolbar or the menu left it invisible.
• Alt-Enter selects every match while the find widget is open, as it does in VS Code. It is still Run All everywhere else.
• Settings → Packages reads as three jobs: Update, Upgrade, Restore, one button each, with what this release declares listed at the top. The per-package Re-install buttons are gone — a local checkout is installed editable, so code edits are already live, and Update covers a changed dependency or entry point.
• Changing a viewer setting survives a resize. set_viewer_config(glass=False) reverted the next time anything resized the pane — including every Run, which moves the panes. The same held for tools, treeWidth and theme. Fixed in ocp-viewer-core 1.0.3.

---

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).

v0.5.4

First run

Download and Verification

Verify what you downloaded

Download the latest release from the Release page, compute the checksum of the downloaded file

• macOS: shasum -a 256 build123d-studio-*.dmg
• Windows: certutil -hashfile build123d-studio-*.zip SHA256
• Linux: sha256sum build123d-studio-*.AppImage

and compare it against the values in SHA256SUMS.txt on the same Release page.

If the github CLI gh is installed, you can also verify the downloaded files by

gh attestation verify build123d-studio-*.dmg --repo bernhard-42/build123d-studio

Installation

Install it the ordinary way for your platform: drag the .app to Applications under MacOS, unzip the Windows package or store the Linux AppImage where you like it.

Running the application

Preparation:

• macOS: MacOS builds are signed ad hoc, with no Developer ID and no notarisation. So, the first run is blocked with

  "build123d Studio" Not Opened
  Apple could not verify “build123d Studio” is free of malware that may harm your Mac or compromise your privacy.

  Open "System Settings / Privacy & Security" and under Security you find

  "build123d Studio" was blocked to protect your Mac'.

  Click on "Open Anyway".

  Alternatively, run xattr -dr com.apple.quarantine "/Applications/build123d Studio.app" before double clicking the build123d Studio icon.

• Windows: Windows builds are unsigned, hence SmartScreen warns on first run. Use More info → Run anyway.

• Linux: Neutralino uses the system webview rather than bundling a browser engine. It tries to load libwebkit2gtk (version 4.0 or 4.1).

  • Install WebKitGTK (libwebkit2gtk-4.1-0 or libwebkit2gtk-4.0-37 on older releases) if it is not already there, see neutralinojs dependencies.
  • Mark the AppImage executable, or the desktop treats it as a data file and offers to open it with an archive manager: chmod +x build123d-studio-*.AppImage.

The first start takes a few minutes and shows you what it is doing. A splash overlay reports each step while it downloads uv, downloads the Python interpreter, and installs the Python packages (several hundred megabytes in total, including the language server and the OpenCascade bindings). Everything is downloaded into your user data directory:

• macOS: ~/Library/Application Support/build123d-studio/
• Windows: %APPDATA%\build123d-studio\
• Linux: ~/.local/share/build123d-studio

Every start after that goes straight to the window. The environment already exists, so all that happens is a reconciliation against the locked package list, and the window is up while the kernel warms in the background. The kernel indicator in the toolbar says starting, then idle, and you can type before it gets there.

Troubleshooting

If something goes wrong, consult the log in the user data directory (see above).