Sim Plugin Workbench — Development skill for Claude Code

sim-plugin-workbench

Use Codex, Claude Code, or another AI agent to orchestrate [Ansys Workbench](https://www.ansys.com/products/ansys-workbench) projects from the workflow you already use.

`sim-plugin-workbench` gives an agent practical Workbench control paths: create and update analysis systems, run Workbench journals, inspect live session health, summarize systems and cells, manage project checkpoints, and hand the Model cell off to solver-specific plugins such as Mechanical.

The Workbench application and SDK are not bundled. Bring your own Workbench installation. See [LICENSE-NOTICE.md](LICENSE-NOTICE.md).

What an agent can do with Workbench

• Create or update Workbench analysis systems through journals.
• Keep Engineering Data, Geometry, and Model cells organized before solver work.
• Use a persistent PyWorkbench session when the SDK is available.
• Fall back to RunWB2 journal execution when the SDK path is unavailable.
• Inspect session health, UI capabilities, project identity, and system/cell state before continuing a workflow.
• Prepare a clean handoff to Mechanical for setup, solve, and result extraction.

Choose the right Workbench workflow

1. Persistent SDK session

Use this for repeatable agent-driven orchestration:

uv run sim connect --solver workbench --ui-mode gui
uv run sim inspect session.health
uv run sim exec --file step.wbjn
uv run sim inspect workbench.systems.summary

The SDK path is preferred because it keeps state across steps and lets the agent inspect Workbench state between bounded journal snippets.

2. RunWB2 fallback

Use this when the SDK is unavailable or incompatible:

uv run sim run --solver workbench path/to/journal.wbjn

RunWB2 is reliable for one-shot journals, but it should not be treated as a rich live session. Inspect the JSON result written by the journal and save a project checkpoint before handing off to another solver.

3. Workbench-to-Mechanical handoff

Use