Troubleshooting COMSOL through sim-cli
COMSOL not detected
Section titled “COMSOL not detected”- Symptom.
sim check comsolreports the solver as missing or unreachable;sim connect --solver comsolfails immediately. - Diagnostic.
uv run sim plugin doctor comsol --deep. - Likely fix. Confirm a licensed COMSOL Multiphysics install is on
the host, and that the
comsollauncher is onPATHor pointed at by the documented environment variable for your install layout.
License unavailable
Section titled “License unavailable”- Symptom.
sim connectopens then immediately exits with a license-server error in the log;sim check comsolmay pass because the binary is found but a license seat is not. - Diagnostic. Run COMSOL once outside sim-cli to confirm interactive
licensing works, then
uv run sim plugin doctor comsol --deep. - Likely fix. Check FlexLM / network-license configuration with your
IT team; sim-cli does not proxy license traffic, so anything that
breaks
comsolstandalone will also break the sim-cli session.
Desktop session not attached
Section titled “Desktop session not attached”- Symptom. Agent runs through sim-cli succeed but you see no COMSOL Desktop window, or the engineer’s GUI window does not reflect the agent’s actions.
- Diagnostic.
uv run sim inspect session.healthwhile the session is open. - Likely fix. Reconnect with the shared-desktop visual mode for your workflow; headless and shared-desktop are distinct session types and cannot be converted mid-session.
Model identity mismatch
Section titled “Model identity mismatch”- Symptom. Agent reports changes to the model but a re-inspection shows the old state, or two parallel sessions disagree about parameters.
- Diagnostic.
uv run sim inspect session.summaryand confirm the reported.mphpath is the file the agent thinks it edited. - Likely fix. Close stray sessions, reopen against the canonical
.mphpath, and save a checkpoint immediately after the next successful step so the agent has a known-good anchor.
Agent guessing COMSOL API names
Section titled “Agent guessing COMSOL API names”- Symptom. Agent invents method or property names that don’t exist
in the COMSOL Java/Python API;
sim execfails with attribute errors. - Diagnostic. Re-read the bundled sim-comsol skill in
.agents/skills/sim-comsol/(or.claude/skills/sim-comsol/). - Likely fix. Re-prompt the agent with: “Do not guess COMSOL API
names. Inspect the model first, then use only names returned by the
inspection.” If the skill is missing, re-run
uv run sim plugin sync-skills --target .agents/skills --copy.