sim-plugin-comsol 0.1.13

COMSOL Multiphysics driver for sim-cli, distributed as an out-of-tree plugin

sim-plugin-comsol

Use Codex, Claude Code, or another AI agent to work with COMSOL Multiphysics models from the workflow you already use.

sim-plugin-comsol gives an agent practical COMSOL control paths: inspect saved .mph files, attach to a visible COMSOL Desktop session, build or modify models through the COMSOL Java API, run studies, check live-session health, and export results while the engineer can keep watching or intervening in COMSOL Desktop.

The COMSOL solver and its mph Python binding are not bundled — you supply and license COMSOL yourself. See LICENSE-NOTICE.md.

What an agent can do with COMSOL

• Help with a model you already have open in COMSOL Desktop.
• 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, Desktop attach helper, and bundled COMSOL skill. A receiving agent should not need a separate COMSOL skill checkout.

Choose the right COMSOL workflow

1. Agent-owned live Desktop session — best for repeatable work

Use this when the agent should build, inspect, solve, and debug a model across multiple steps while the engineer watches a live COMSOL Desktop client:

sim connect --solver comsol --ui-mode gui --driver-option visual_mode=shared-desktop
sim inspect session.health
sim exec --file step.py

shared-desktop starts comsolmphserver, attaches a full COMSOL Desktop client to that server, and binds agent snippets to the Desktop active model tag. session.health should report model_builder_live: true and a live_model_binding.ok value of true before relying on the GUI as a live view of agent edits.

Prefer this path for reliable multi-step model building, solving, structured inspection, and repeatable agent workflows.

2. User-owned Desktop attach — best for small visible edits

Use this when the user already opened COMSOL Desktop normally, loaded their .mph, opened Java Shell, and wants an agent to make a small visible edit or run a quick human-in-the-loop check inside that same Desktop window:

sim-comsol-attach open --json --timeout 120
sim-comsol-attach health --json
sim-comsol-attach exec --file step.java --json

The Desktop attach helper submits COMSOL Java Shell text to the visible user session. It is intentionally conservative: it should help with bounded edits and quick checks, but it should not be treated as proof that a full solve or long workflow succeeded unless the agent verifies the resulting COMSOL state or artifacts.

3. 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?"

Install

pip install sim-plugin-comsol

You can also install through sim-cli's plugin command:

sim plugin install sim-plugin-comsol

After installation, sim-cli auto-discovers the COMSOL driver and bundled skill:

sim drivers | grep comsol
sim check comsol
sim run --solver comsol path/to/script.py

Agent quickstart

Give Codex, Claude Code, or another coding agent this instruction when the task is about COMSOL:

Use the bundled COMSOL skill from sim-plugin-comsol. First identify whether the
user wants: (1) a reliable agent-owned shared Desktop session, (2) a small edit
inside an already-open COMSOL Desktop via Java Shell attach, or (3) offline
inspection of a saved .mph file. For reliable visible co-editing, use
`sim connect --solver comsol --ui-mode gui --driver-option visual_mode=shared-desktop`
and verify `session.health.live_model_binding.ok`. Use Java Shell Desktop
attach only for already-open ordinary Desktop sessions, small edits, or
human-in-the-loop fallback work. For non-trivial modeling, establish the target
model identity and working folder first: load the given .mph, or set a
descriptive model tag/title and save an early checkpoint .mph under a case
workdir. Build and solve the requested model one bounded step at a time.

The bundled skill entry point is:

src/sim_plugin_comsol/_skills/comsol/SKILL.md

How it relates to sim-cli

sim-plugin-comsol is a Python package that extends sim-cli. sim-cli provides the common agent runtime surface (connect, exec, inspect, screenshot, run), while this plugin supplies the COMSOL-specific driver, Desktop attach command, and COMSOL agent skill.

The plugin registers the Desktop attach CLI plus three entry-point groups:

[project.entry-points."sim.drivers"]
comsol = "sim_plugin_comsol:ComsolDriver"

[project.entry-points."sim.skills"]
comsol = "sim_plugin_comsol:skills_dir"

[project.entry-points."sim.plugins"]
comsol = "sim_plugin_comsol:plugin_info"

[project.scripts]
sim-comsol-attach = "sim_plugin_comsol.desktop_attach.cli:main"

sim.drivers exposes the driver class; sim.skills exposes a directory of skill files bundled inside the wheel; sim.plugins exposes plugin metadata for discovery. sim-comsol-attach exposes the Desktop-first collaboration path.

Develop

git clone https://github.com/svd-ai-lab/sim-plugin-comsol
cd sim-plugin-comsol
uv sync
uv run sim drivers
uv run sim check comsol
uv run pytest

License

Apache-2.0. See LICENSE and LICENSE-NOTICE.md.