Skip to content

ALTERED BRILLIANCE IS LIVE ON GOOGLE PLAY. Read the product story

Kri Zek
CODENAMEDEACON / KRIFORGE WORKBENCH

Build the game,not the busywork.

CodenameDeacon is surfaced as KriForge: an AI-native desktop workbench for game development, with local workspace context, deliberate agent workflows, and engine-aware planning.

SCROLL
A GAME-NATIVE WORKBENCH

Context should be earned, not scraped.

CodenameDeacon is the development module behind KriForge. It begins with the files, rules, diagnostics, and engine signals a developer has deliberately opened to the workbench, making planning, inspection, and safe changes legible before an agent acts.

Windows desktop previewCode OSS migration in progressLocal indexing by default
THE WORKBENCH TODAY

One loop, fewer blind spots.

The current product foundation combines a local desktop shell with the surfaces a modern game team needs to understand its project before making changes.

WORKSPACE CONTEXT

Index with boundaries

Scan project files under explicit ignore rules, keep a local search fallback, and make workspace context inspectable before it is used.

#Workspace index#.kriforgeignore#Search
AI WORKFLOW

Plan, review, then apply

Use chat, composer plans, artifacts, checkpoints, and diff-preview primitives to keep an AI-assisted change understandable.

#Composer#Diff preview#Artifacts
GAME AWARENESS

Recognize the project shape

Detect Unity, Unreal, Godot, and KriZek2D project signals, then prepare engine-specific tasks and launch configurations.

#Project detection#Task generation#Launch profiles
A QUIETER KIND OF AI

Useful only when the developer remains in control.

RISK CLASSIFICATION

Commands are classified so high-risk actions can be surfaced for review rather than blended into a generic chat response.

DIFFS & CHECKPOINTS

Changes are designed to have visible diff review and checkpoint primitives; full rollback remains a planned capability.

LOCAL-FIRST DEFAULTS

Product metadata defaults AI telemetry off, remote context off, and local indexing on until an operator makes a conscious change.

01

Open the workspace

Begin with a local project and its explicit rules, instead of an opaque cloud-only project representation.

02

Connect the game loop

KriForge can prepare tasks, diagnostics, and context for supported engine profiles, including the KriZek2D bridge.

03

Ship with evidence

The workbench direction includes visible plans, task results, and validation artifacts rather than a black-box “done” state.

KRIFORGE DESKTOP PREVIEW

Make the development loop more deliberate.

Request desktop-preview access, or explore the native engine KriForge is designed to understand. Availability, signing, and update infrastructure will be announced separately.