Modex documentation
Modex is a workspace for modeling and simulation, with optional AI assistance. It edits plain Modelica .mo files on your disk, runs them with OpenModelica or Dymola, and turns the results into figures and documents. In VS Code it can also open PSCAD .pscx projects through the separately installed AgenticEMT package.
These pages cover installing Modex, connecting it to a simulation engine, and fixing what goes wrong. They are short on purpose: the editors explain themselves, and these pages answer the questions they cannot.
Choose how you use Modex
| You want to… | Start here |
|---|---|
| Work in VS Code, Cursor, Windsurf or another editor built on VS Code | VS Code extension |
| Use a standalone Windows app (public preview) | Modex Desktop |
| Give Claude Code, Codex, Claude Desktop or another MCP client Modex's modeling tools | Claude Code, Codex & MCP |
AI is optional in every form. The editors, libraries, simulation and result tools work without an AI provider.
Then
- Simulation engines — install OpenModelica, or point Modex at Dymola.
- PSCAD projects — install AgenticEMT and open a
.pscxin place (preview, VS Code and Desktop). - Examples — open-source Modelica models to run, from power systems to mechanics.
- Troubleshooting — where the logs are, and what to send when you report a problem.
What Modex opens
| File | What it is |
|---|---|
.mo | a Modelica model or package — diagram, icon and text views of the same file |
.pscx | a PSCAD project, edited in place by AgenticEMT (VS Code, preview) |
.drawio | a general diagram, edited offline in a bundled draw.io |
.mxfig | a figure: plotted signals from one or more simulation runs |
.mxdoc | a document: prose with plots linked to figures or pinned to a run |
Getting help
- Discord — discord.gg/M6UV96F739
- Bug reports and feature requests — github.com/modexai-io/modex-feedback
- Email — support@modexai.io