Take an enclosure for a Raspberry Pi cluster, for example. Nothing fancy - just four standoffs, a few ventilation slots, a lid that snaps on. The kind of thing you model in OpenSCAD because you want parametric control, not a mouse-driven 3D editor.
The OpenSCAD editor got in the way. The editor’s completion is basic. No inline error checking - you write, you hit render, you read the console output, you go back and fix the typo. No navigation. No refactoring. It is a text editor from 2008 with a 3D viewport bolted on.
So I built a JetBrains plugin for OpenSCAD.
What it adds
Syntax highlighting was the easy part. The interesting work was building a parser for OpenSCAD’s grammar and integrating it with the PSI tree so that the IDE understands the code structurally. That gives you completion on module names and parameters, go-to-definition, find usages, inline error highlighting before you render. The things you take for granted in Java or Python but that OpenSCAD developers have never had.
I also added structure view - a sidebar that shows your modules and functions in a tree. When your file grows past 500 lines, and parametric models grow past 500 lines faster than you think, that becomes essential.
A small audience, and that is fine
The OpenSCAD community is small. It will probably stay that way. OpenSCAD is a niche tool inside a niche hobby inside a niche of software development.
I keep maintaining it because I use it myself. Every hardware project I build starts in OpenSCAD. And because taking a plugin offline feels wrong when people depend on it, even if those people are not many. Some of my most thoughtful bug reports come from this plugin’s users.
The IntelliJ Platform is powerful enough that maintaining an additional language plugin costs me little. The shared infrastructure across all 22 plugins handles the heavy lifting. Adding OpenSCAD-specific inspections on top of that is straightforward.
A modeling language is different
Most of the languages I support in JetBrains are general-purpose or web-oriented. OpenSCAD is different - it is a modeling language where the output is geometry, not text or a UI. The challenge is that errors in a modeling language often look correct syntactically but produce wrong geometry. The plugin catches syntax and type problems. It cannot tell you that your enclosure lid is 2mm too short. That part is still on you.