Gamibase product docs
Gamibase is a local-first, AI-native operations toolkit for Unreal Engine teams. It gives Unreal-aware structure, diagnostics, and workflow intelligence that makes downstream LLM or operator decisions better — across CLI, MCP, VSCode, and an optional UE Plugin Bridge.
The core wedge is Build Doctor: take a failed Unreal build, classify the failure, package ranked evidence with ownership and dependency context, and surface explicit next steps so the downstream LLM, agent, or operator can carry out the right fix.
From install to first diagnosis in four steps.
- 01
Install and verify Gamibase
Install the CLI with winget or the hosted PowerShell script, then run gamibase version and gamibase install-status to verify the machine runtime and inspect explicit deferred or blocked optional surfaces.
- 02
Start with Build Doctor
Point Gamibase at a failed Unreal build or log. Build Doctor classifies the failure, packages ranked evidence with file, line, and module context, and surfaces next steps so the downstream LLM or operator can decide what to do.
- 03
Explore project intelligence
Use project-aware reads to inspect structure, build config, and error context. Deeper intelligence — symbols, hierarchy, Blueprint exposure, config files — is available with Pro.
- 04
Bind a project and choose your surface
Run gamibase init for each Unreal project that should expose project-local MCP config, then choose the entry point that fits your workflow. CLI, MCP, VSCode, and CI still share the same trust rules, evidence gates, and edition boundaries.
One CLI for Unreal-aware structure, logs, diagnostics, and controlled workflow planning.
Gamibase supplies structure, logs, diagnostics, and Unreal-aware intelligence. The downstream LLM, agent, or operator owns final patching and code implementation. All commands support --json for scripting and CI.
Install & Onboarding
Public CLI entrypoints for Windows setup and project binding.gamibase version --jsonCommunityVerify that the installed Gamibase CLI and MCP runtime are present on the machine.
gamibase install-status --jsonCommunityInspect multi-surface install state and explicit deferred or blocked optional targets after machine install.
gamibase init --project-root "<path>" --jsonCommunityBind the installed runtime to one Unreal project by writing project-local MCP client configuration.
Community
Free. Core diagnosis and project intelligence.gamibase doctorCommunityDiagnose failed Unreal builds and package structured evidence with explicit next steps.
gamibase infoCommunityRead project structure: .uproject, modules, targets, plugins, and layout.
gamibase configCommunityRead build-target configuration, platform settings, and related build context.
gamibase errorsCommunityParse and structure compile/build errors into normalized Unreal-aware findings.
gamibase authCommunityResolve entitlement/access state and licensing posture.
gamibase telemetryCommunityControl telemetry state.
Pro
Paid. The day-to-day Unreal operator toolkit.gamibase searchProSearch source-wide Unreal symbols and ownership context.
gamibase hierarchyProTrace class ancestry and inheritance relationships.
gamibase analyze-blueprint-exposureProInspect Blueprint-facing reflected C++ surfaces.
gamibase read-config-filesProRead Unreal config files with redaction-aware intelligence.
gamibase crashProAnalyze crash evidence and package follow-up guidance.
gamibase featureProTurn a feature request into Unreal-aware implementation guidance and placement hints.
gamibase reviewProReview code with Unreal-specific heuristics and evidence packaging.
gamibase buildProPlan and orchestrate Unreal-aware build workflows.
gamibase diagnose-buildProRun higher-detail build diagnosis and evidence synthesis.
gamibase cookProProduce cook planning and execution guidance under explicit workflow modes.
gamibase packageProProduce packaging planning and execution guidance under explicit workflow modes.
gamibase testProDiscover and orchestrate automation test workflows.
gamibase importProProduce import preflight and bridge handoff guidance.
gamibase validateProProduce validation preflight and bridge handoff guidance.
gamibase mcp-routesProInspect MCP route inventory and runtime metadata.
gamibase parityProInspect local/CI parity artifacts and drift checks.
gamibase extension-scaffoldProValidate extension/runtime scaffold state.
Studio
Pro + governance, policy, and team controls.gamibase governanceStudioExpose governance, policy state, and team-control surfaces.
From failed build to structured diagnosis in one command.
Build Doctor is the clearest entry point into the product. It detects, parses, locates, and packages evidence for Unreal build failures so the downstream LLM or operator can make better fix decisions.
- 01
Detect
Accept a build log or error output — from file, stdin, or a stream.
- 02
Parse
Structure compile errors with deduplication and error family extraction (missing includes, module deps, UHT specifiers, linker errors, and more).
- 03
Locate
Identify the owning code using symbol search and class hierarchy. Record similar past failures via pattern memory.
- 04
Evidence
Package ranked findings with file/line ownership, module context, confidence scores, and eligibility classification. The downstream LLM or operator owns final fix-strategy decisions.
Five operator surfaces, one product model.
CLI
Available nowMCP Runtime
Available nowVSCode Extension
Available nowCI
Available nowUE Plugin Bridge
In developmentA local-only bridge into Unreal Editor — not a second UI.
Without the plugin, Gamibase reads project files, build configs, source code, and logs from disk. With the plugin, it can also read Blueprint data that only exists inside the editor, validate assets using editor-aware knowledge, and run a small set of approved editor-side actions. VSCode remains the main operator surface.
Blueprint summary export
Carried from PRDCompact JSON summary of Blueprint graphs, variables, functions, and components for VSCode and MCP routes.
Blueprint deep export
ProposedFull node, pin, and graph detail on opt-in. Selective expansion and chunked reads prevent payload bloat.
Live Blueprint sync
ProposedStream Blueprint deltas to VSCode as the developer edits in Unreal. Delta-first, subscribe-only, rate-capped.
Asset validation
Carried from PRDValidate naming conventions, material slots, LODs, collision, and reference integrity using editor-aware knowledge.
Blueprint-to-C++ assistance
ProposedPreview feasibility, generate candidate C++ with confidence tiers, and optionally reparent after explicit approval.
Editor context
ProposedQuery current map, selected assets, PIE state, and open Blueprints so workflows have live editor context.
- Bridge, not interface — VSCode remains the main operator UX
- Local-first and fail-closed — no remote exposure
- Summary-first by default — large payloads require explicit opt-in
- Diff-first for writes — scan, plan, confirm, apply, verify
- Small editor footprint — only the minimum Unreal UI needed
What is current, qualified, and still future-looking.
Core diagnosis and intelligence
Day-to-day operator toolkit
Pro + governance and policy controls
Safety rules are baked into every workflow, not bolted on after.
Gamibase is an evidence-and-intelligence layer, not a code-mutation product. These principles are non-negotiable and apply across every surface and every edition.
Evidence and intelligence, not code mutation
Gamibase gathers structure, logs, diagnostics, and Unreal-aware intelligence. The downstream LLM, agent, or operator owns final patching and code implementation.
Default behavior: diagnose and report, not modify
Running gamibase doctor produces an evidence report with ranked findings and next steps. It does not apply patches, create branches, or run builds.
Evidence gates with freshness enforcement
Higher-impact workflows require current evidence with project and session binding. Stale or missing evidence returns a deterministic block code with remediation guidance.
Fail closed when state is stale or unsupported
When the workflow should stop, it stops. Destructive or unsupported paths refuse to proceed on stale, missing, or disconnected state.
One product across surfaces
CLI, MCP, VSCode, and CI are different entry points into one system. Same trust rules, same evidence requirements, same edition boundaries.
Which edition fits your workflow.
Gamibase ships three editions. They share the same surfaces (CLI, MCP, VSCode, CI) and the same trust model. The difference is scope: how much intelligence, how many workflows, and whether governance controls are included. Access is account-linked across surfaces, and Studio onboarding remains manual until team administration is fully launched.
Community
Individual developers evaluating Gamibase or teams that only need core diagnosis and project reads.
Community gives you Build Doctor in diagnose-only mode, project structure and build config reads, and structured error parsing. You have full access to CLI, MCP, VSCode, and CI — but the scope is intentionally narrow. Community is the starting point, not the full toolkit.
Community does not include source-wide symbol search, class hierarchy, crash analysis, feature planning, code review, or any workflow orchestration (build, cook, package, test). Those capabilities drive Pro.
Pro
Individual developers or small teams using Gamibase as their day-to-day Unreal operations layer.
Pro unlocks the full intelligence and orchestration surface. That includes source-wide symbol search, class hierarchy, Blueprint exposure analysis, crash analysis with evidence packaging, feature planning, code review with Unreal heuristics, and build/cook/package/test workflow orchestration. Pro also adds higher-detail build diagnosis, redaction-aware config file reads, import and validate preflight routes, and local/CI parity checks.
Pro does not include governance, team-wide policy controls, or approval workflows. If your team needs operation allowlists, audit export, or policy enforcement across a group of operators, that is Studio territory.
Studio
Team leads, studio ops, and organizations that need governance and policy controls on top of the Pro toolkit.
Studio includes everything in Pro and adds governance dashboard access, team-wide operation allowlists and deny policies, approval workflows, audit export, compliance controls, and model governance alignment. Studio is the edition where a lead or admin can define what operators are allowed to do and enforce it across the team.
Studio does not create a separate product tree. It is Pro with governance and policy depth layered on top. If you do not need team-wide policy controls, Pro is the right edition.