Sim Plugin Comsol — Development skill for Claude Code

sim-plugin-comsol

Use Codex, Claude Code, or another AI agent to work with [COMSOL Multiphysics](https://www.comsol.com) models from the workflow you already use.

`sim-plugin-comsol` gives an agent practical COMSOL control paths: inspect saved `.mph` files, search local COMSOL documentation, run saved models through `comsolbatch`, compile settled Java recipes with `comsolcompile`, build or modify models through the COMSOL Java API, and work through a shared visible COMSOL Desktop session when the engineer wants to watch or intervene.

COMSOL itself and its `mph` Python binding are not bundled. See [LICENSE-NOTICE.md](LICENSE-NOTICE.md).

What an agent can do with COMSOL

• Load and modify existing COMSOL .mph models.
• Search installed COMSOL help for module, API, and example-model details.
• Run saved models directly with COMSOL's own batch executable.
• Compile and run settled Java build-solve-extract recipes.
• Build and solve a model step by step while you watch the Model Builder.
• Inspect a saved .mph file before deciding what to change.
• Run bounded edits, checks, plots, and result-export steps through COMSOL's Java API.
• Keep a structured audit trail of commands, health checks, and generated artifacts so results can be reviewed rather than guessed.

This repository is intended to be the complete COMSOL agent bundle: driver and bundled COMSOL skill. A receiving agent should not need a separate COMSOL skill checkout.

Choose the right COMSOL workflow

1. Saved `.mph` inspection — best before changing a file

When the user only needs to know what is in a saved COMSOL model, use the bundled offline inspection helpers before launching a heavyweight COMSOL session. This is the right first step for questions like: "what physics, parameters, studies, meshes, and result nodes are in this `.mph`?"

2. Direct `comsolbatch` — best for saved-model runs

Use COMSOL's own executable when the task is a deterministic saved-model run or fan-out ove