svd-ai-lab/sim-cli
CLI-first runtime for Codex, Claude Code, and AI agents to operate CAE solvers via plugins: COMSOL, Abaqus, Ansys.
2 Releases
Latest: 1mo ago
v0.3.5Latest
๐ฆ Summary
- Reframed the public README around uv-first, project-local agent setup.
- Added first-class Windows-safe setup wording without duplicating identical uv commands.
- Updated plugin installation docs to prefer `uv add ...` and `uv run sim ...`.
- Removed global CLI setup guidance from the user-facing path to keep the docs agent-oriented.
- Clarified agent handoff prompts to use installed solver skills without hard-coding skill paths.
๐ฆ Package
- PyPI: https://pypi.org/project/sim-cli-core/0.3.5/
- Distribution: `sim-cli-core==0.3.5`
v0.3.0 โ pure plugin architecturev0.3.0
๐ฅ Breaking change
- After upgrading, `sim-cli-core` ships zero built-in drivers. To use any solver, install its plugin:
- ```sh
- sim plugin install <name> # e.g. ltspice, coolprop
- sim plugin list # see what's available + installed
- ```
- `sim plugin install` resolves short names against the curated plugin index at https://github.com/svd-ai-lab/sim-plugin-index. Private plugins can be installed via `git+https://...` URLs.
๐ฆ Why
- Solver-side libraries (vendor SDKs, file-format parsers) move on their own cadence; bundling them in sim-cli was forcing every release to wait on them.
- Each plugin pins its own solver-side deps, eliminating cross-repo release skew.
- Closed-source / commercial-license drivers can ship privately without bloating the public sim-cli repo.
๐ฆ Migration for existing users
- If you previously relied on a built-in driver, install its plugin once:
- ```sh
- sim plugin install ltspice # (or whichever solver you use)
- ```
๐ฆ Highlights since v0.2.4
- #78 โ empty `_BUILTIN_REGISTRY`; pure plugin architecture
- #77 โ drop stale `[pybamm]` optional-dependency extra
- #79 โ document private-plugin install path in README
