Optional editor-side bridge for deeper Unreal-native flows when that phase is active and explicitly scoped.
Editor-owned boundary for deeper workflow depth. Direction is defined without overclaiming current depth. Current capabilities stay separate from bridge-specific depth. Richer editor-native execution remains explicitly deferred
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.
Editor-native depth needs an explicit bridge boundary, not vague claims about hidden automation.
Editor-side ownership
Deeper Unreal-native workflows need a bridge that makes editor responsibility explicit instead of implied.
Claim discipline
Current baseline workflows should stay separate from later editor-native depth.
Phase separation
Bridge work needs clear boundaries so present-tense messaging stays honest and usable.
Trust continuity
Deeper editor-side actions still need to inherit the same review-first trust posture as every other surface.
UE bridge direction that stays useful without overstating unfinished depth
Optional editor-side boundary
The bridge defines where deeper editor-native work belongs when that phase becomes active.
Same product rules
Future bridge depth is still expected to follow the same visible trust model.
Boundary is defined
The direction is real, but current language stays measured and clearly deferred.
Deeper execution is deferred
Richer editor-native workflow depth remains roadmap territory rather than a present-tense flagship claim.