Editor surface for daily project work, with panels, commands, and reports backed by the same workflow engine.
Command Center and Smart Context panels. Report rendering, auth, and telemetry controls. Editor-native entry points for diagnosis and review. Familiar workflow behavior inside VSCode
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.
Editors can host commands. Unreal teams need sharper context inside the work surface they live in.
Context switching
Leaving the editor for diagnosis, project reads, and workflow follow-up slows down technical work.
Disconnected tools
Operators do not want separate interfaces for diagnosis, reports, trust controls, and project context.
Weak workflow continuity
Editor experiences break down when they do not carry the same product rules as terminal and agent surfaces.
Trust shortcuts
Editor-native UX still has to respect the same review posture and execution limits as the rest of the product.
VSCode that feels productized without becoming a separate product
29 command contributions
Broad command coverage for day-to-day workflow entry points inside the editor.
Command Center and reports
Surface diagnosis, context, and operator controls in a more usable daily-driver experience.
Shared runtime underneath
The editor surface stays aligned with the same contracts used everywhere else.
Visible trust posture
Review boundaries and access posture stay intact even when the UX feels smoother.