Terminal-first surface for local runs and CI parity. Clear modes, review checkpoints, and structured output.
Diagnose builds, inspect project context, and run workflow commands from one shell. Same command shape in local work and CI jobs. Dry-run, preflight, and gated steps stay explicit. Script-friendly output for operators and automation
Runtime entries
24
Runtime entries
Canonical product actions spanning diagnosis, project reads, workflows, auth, and governance.
MCP tool routes
20
MCP tool routes
Machine-facing routes for Unreal-aware reads, diagnosis, and governed workflow access.
VSCode actions
29
VSCode actions
Editor-native command coverage with the same runtime and trust model underneath.
Surface types
5
Surface types
CLI, MCP, VSCode, CI, and the optional UE bridge.
Generic shells can run commands. Unreal teams need clearer operator workflows.
Noisy build output
UBT and UHT failures bury the actual issue under Unreal-specific output that generic shell tooling does not interpret well.
Project-specific complexity
Targets, modules, and engine conventions require more context than ordinary scripts can safely assume.
Local and CI drift
Teams need the same product behavior in a terminal and in a pipeline, not two separate execution stories.
Trust visibility
Review gates, dry-run posture, and fail-closed behavior need to stay obvious before high-impact actions.
CLI that keeps the product model direct and explicit
Terminal-first operation
Build, diagnose, and route workflow actions from one direct operator surface.
Local and CI parity
The same runtime model carries from developer machines into pipeline automation.
Script-friendly output
Text-first commands stay composable without flattening Unreal-specific context.
Review-first execution
Dry-run, preflight, and gated follow-through remain visible in the shell experience.