osmatrix
osmatrix: local OS guests + local GitHub Actions
osmatrix gives you three kinds of guests (check env_status for what this host has):
| guest | what it is | shell for env_exec |
|---|---|---|
ubuntu |
container from the same image act uses for ubuntu-* jobs |
bash |
windows |
Windows Server VM (dockur/QEMU) | PowerShell 7 (pwsh) |
macos |
macOS VM (dockur on Linux, tart on Apple Silicon) | zsh/bash |
and local CI: workflow matrices expanded into legs. ubuntu-* legs run with act on the host's Docker; windows-* / macos-* legs run act inside the matching VM (host mode), after syncing the repo into it.
Use the MCP tools (ci_plan, env_exec, ...) when they are available: they are the supported interface, and their safety annotations let the client ask for confirmation where it matters.
If the osmatrix MCP tools are missing from this session, tell the user before doing anything else. Say that the osmatrix MCP server isn't loaded, so you'll use the osmatrix CLI instead, and suggest the likely fix: enable or restart the osmatrix MCP server in the client's MCP/plugin settings (a server that failed once may stay failed until it is toggled off and on). Then continue with the CLI: every tool has a matching command (see reference.md); add --json for machine output. Check osmatrix --version first; if the command isn't found, npx -y osmatrix@0 <command> works once osmatrix is published on npm. Otherwise tell the user it isn't installed, and stop.