Majestic Helios is an AI-native Windows IDE being built specifically for game development and the Majestic ecosystem.
Loading page
Loading page content
ALTERED BRILLIANCE IS LIVE.ALTERED BRILLIANCE IS LIVE ON GOOGLE PLAY.Read the product story →
Formerly KriForge, Majestic Helios is a Windows-native, Code OSS-based game development IDE for local context, reviewable AI workflows, durable sessions, and a tighter connection to Majestic Engine.
Majestic Helios is designed to connect consented gaming evidence with the project itself: code, scenes, assets, shaders, configuration, diagnostics, builds, tests, logs, and runtime state.
Start with a defined player or game question and only the context approved for that workflow.
Relate the signal to the systems, content, runtime state, and diagnostics that can explain it.
Plan, inspect, approve, test, and hand the work to Majestic Engine without turning creation into a black box.
Majestic Helios is the upgraded public identity for the workbench previously known as KriForge. Its supported product shell is native Code OSS and Monaco; the browser and Electron workbench remains development tooling rather than the final user-facing editor.
Majestic Helios combines the native editor shell with explicit context, safety, source control, and engine integration boundaries.
Index the opened workspace under explicit ignore rules, preserve a local search fallback, and keep remote context and AI telemetry off by default.
Use chat, composer plans, artifacts, risk classification, approval-gated tools, checkpoints, and visible diffs before a mutable action lands.
Use a versioned, file-backed bridge for editor state, play controls, validation, selection, scene opening, node creation, and path-safe source handoff.
Restore open tabs, active state, unsaved content, and dirty markers for the selected workspace, with guards before destructive closes or reverts.
Navigate matches, replace the current result, replace all results, and use familiar keyboard shortcuts inside the workbench editor.
Create files and folders, rename or delete workspace entries, open multiple files, and launch another desktop window from the shell.
Inspect status, stage all, unstage all, and commit with a required message through standard Git commands.
The IDE begins with a local workspace and its explicit rules, not an opaque cloud-only project representation.
File writes, creation, movement, deletion, terminal actions, and trusted tool paths remain subject to explicit control boundaries.
Plans, diffs, task results, diagnostics, and validation artifacts keep the work legible instead of collapsing it into a black-box done state.
Majestic Helios currently targets Windows and remains a developer preview. The latest Helios commit has local validation evidence, but no GitHub status checks because automatic push CI was previously disabled.
The installer is not presented as signed or publicly released. Unity and Unreal integrations remain future adapters; Godot is deferred. Majestic Engine is the active first-party integration.
With player approval, structured gameplay evidence can move through tGiX and the scoped TGX-1 API into Majestic Helios. The IDE can place that context beside plans, diffs, diagnostics, and engine state so decisions stay reviewable.
Helios helps developers investigate patterns and shape changes with local context and explicit approvals.
Majestic Engine remains responsible for authoring, execution, validation, and runtime behavior.
Beta direction / scoped access / no claim of autonomous game design
Prove the first-party Majestic workflow, then extend the IDE through deliberate engine adapters.
Reviewed August 2026 · no fixed release dates
View portfolio roadmapPublicly shipped or part of the current product foundation.
Code OSS workbench, local context, Git, persistent sessions, and reviewable AI changes.
Direct Majestic Engine project and bridge foundations keep code, diagnostics, and engine state in one development loop.
Source exists, but runtime, packaged, or release acceptance is incomplete.
Restore green CI, then prove the native build, browser verification, account persistence, and packaged Windows workflow.
Dependency: Blocked until the current npm installation failure is resolved.
Prove plan, approval, tool use, repair, build, test, preview, and final reporting with real runtime evidence.
Approved work is actively being built or hardened.
Add authenticated connection state, heartbeat, version and capability negotiation, acknowledgements, diagnostics, and reliable build/run control.
Validate native sign-in, refresh, restart persistence, device registration, entitlements, and hosted usage.
Intended direction, subject to validation, sequencing, and change.
Bring engine-aware project context, build results, logs, play controls, and reviewable AI workflows to Unity projects.
Dependency: Begins after the first-party Majestic bridge is runtime-proven.
Connect C++ modules, build tooling, editor logs, automation tests, and runtime context through a versioned adapter.
Dependency: Begins after the adapter contract is validated with Unity and Majestic Engine.
Request controlled preview access, or explore the native engine Majestic Helios is designed to understand.
Platform status, engine relationship, AI workflow, and beta access.