Documentation
README
gui โ cross-driver GUI actuation
Whenever the active driver runs with ui_mode=gui (or desktop),
sim serve injects a gui object into your sim exec namespace
alongside session / solver / meshing / model. The object is the
same shape across solvers โ only the process filter differs โ so one
skill serves every GUI-capable driver.
/connect advertises it:
{
"ok": true,
"data": {
"...": "...",
"tools": ["gui"],
"tool_refs": {"gui": "sim-cli/_skills/sim-cli/gui/SKILL.md"}
}
}
If tools doesn't contain "gui", the driver launched headless and
the object is absent โ don't call it.
When to reach for gui
Three scenarios dominate:
This is the opening of the README. Read the full README on GitHub.