← Additional work

Private release candidate / UE 5.8 developer tool

GhostLink

A private Unreal tool for reviewing AI-requested editor changes, approving selected operations locally and inspecting their results.

GhostLink — project artwork. A graphite-and-amber illustration of inspecting a proposed change, not a product screenshot or architecture diagram.

The problem

An editor change can encounter unsaved work or stale state, and an interrupted operation can leave an uncertain result. The person using an AI tool needs to inspect the proposal, decide whether to proceed and see what happened.

My contribution

I define supported editor workflows, approval boundaries and review scenarios, using AI coding tools extensively for C++ implementation and iteration. I review the behaviour and recorded evidence before extending the operation scope.

  • Inspect and plan
  • Approve locally
  • Execute and inspect the result
Workflow overview.

Implementation choices

Use Unreal's tool boundary

GhostLink registers selected operations through UE 5.8's experimental Unreal MCP and Toolset Registry plugins. The operator workspace separates inspection and planning from execution.

Require a local decision

The workflow uses dry-run validation, an expiring one-shot approval and an explicit continuation step. The person at the local approval surface reviews the proposed operation before it proceeds.

Preserve uncertain results

Local operation records retain results across sessions. An uncertain operation remains available for inspection rather than automatic retry. Backup checks compare recorded manifests, hashes and sizes; Unreal restore and loadability require separate acceptance.

Result

The private candidate implements this review-and-approval workflow for selected editor operations, with retained native-editor and MCP validation. I am continuing save/backup and Undo qualification before a broader release.

Availability and scope

GhostLink remains a project-local private release candidate. Save/backup concurrency and Undo provenance still have open qualification work. The repository is unpublished, and the selected-operation checks do not establish a general-purpose autonomous editor.

Project notes reviewed October 7, 2026. Development status is separate from Nexus reception updates.

Back to additional work