Managed desktop app for agentic Unreal workflows, backed by Studio Services and the same runtime contracts.
Desktop cockpit for missions, approvals, evidence, and recovery. Studio Services handles local orchestration behind the app. Core CLI and MCP remain the BYOL path for pro users. Same contracts and trust posture as the rest of Gamibase
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.
Studio app
APP
Studio app
Managed desktop surface for agentic Unreal workflows.
Surface types
5
Surface types
CLI, MCP, Studio, CI, and the optional UE bridge.
Agentic Unreal work needs a dedicated operator surface, not another editor panel.
Mission supervision
Long-running agent work needs visible mission state, recovery, approval, and evidence flows.
Backend ownership
Desktop UX should not own queues, workers, or bridge authority; Studio Services should.
Agentic continuity
Agent sessions, journals, and mission evidence need continuity beyond a single tool invocation.
Trust visibility
Approvals, blocked state, and evidence freshness need to stay visible before high-impact work proceeds.
Studio app surface backed by local services and shared authority
Desktop mission cockpit
A focused app surface for missions, approvals, evidence review, and recovery.
Studio Services bridge
Local backend services own workers, sessions, queues, policies, and service APIs.
Core and UE authority
The app consumes core runtime, MCP, UE bridge, and contract evidence instead of duplicating them.
Visible trust posture
Review boundaries and access posture stay intact in managed app workflows.