Installation

Both Nwiro plugins install the same way as any other Fab plugin. Pick the listing for the product you want, add it to a project, enable the plugin, and restart the editor.

System requirements

Nwiro AI Pro

1. Install from Fab

Fab listing → 

You have two options, both work fine:

• Add to project, from the Epic Games Launcher: open the Fab tab next to your project and click Add. This installs the plugin only for that project.
• Install to engine, same Fab page but the “Install to Engine” variant. Every project using that engine version will see the plugin in the Plugins list. Useful if you switch between prototypes often and don’t want to keep re-adding it.

2. First launch

Open Window → Nwiro Pro from the main menu, or click the Nwiro icon in the toolbar. You’ll see a sign-in screen.

Create a free account, or sign in with Google. New accounts ship with a handful of free prompts. When you run out, top up in Profile → Credits or subscribe to a monthly plan. Credits never expire on monthly plans.

3. Where Pro saves things

• PCG graphs go to /Game/NwiroAssets/{ProjectName}/, versioned as _v1, _v2, etc. So you can always roll back.
• Spline blueprints live as BP_{ProjectName} in the same folder. Reused across iterations so you don’t get one spline per regenerate.
• Generated 3D meshes (from Meshy / Tripo) land in /Game/<mesh-name>/ when you click Import UE5 from the chat.
• Edited blueprints / assets change in place, on the asset you asked for. The editor’s normal undo stack still works.

4. Where Pro saves nothing

• Your sign-in session is stored locally in the plugin’s config, not in your project repo. Safe to commit the project; your teammates get their own sessions.
• The demo pack, if you download it, lives in %APPDATA%/Nwiro/. Not your project.

Nwiro Integration Kit

1. Install from Fab

Fab listing → 

Same Add / Install pattern as any other Fab plugin. One-time purchase; you own it forever.

2. First launch

Window → Nwiro Integration Kit opens the main panel. First time, the Integrations tab in Settings is where you’ll start.

3. Install an AI tool

Settings → Integrations lists the supported AI tools:

• Claude Code (Anthropic)
• Codex CLI (OpenAI)

For Claude, install Claude Code normally, then use Download to fetch its supported adapter.

For Codex on Windows, Node.js 20+ and npm are prerequisites for managed installation. If no supported runtime is detected, click Install. The Kit installs its pinned official runtime into Nwiro’s per-user directory. A compatible global official runtime at the pinned version or newer is reused unchanged; an older compatible global runtime remains usable and offers the optional Install Nwiro-managed runtime action.

On macOS, Codex works exactly as on Windows: click Install to add the official runtime (Node.js 20+ and npm required), which also unlocks GPT-5.6 and GPT-6 Astra. Without it, Codex runs only if a compatible global official runtime is installed; a previously downloaded legacy Zed Codex adapter is no longer used.

When the selected integration is ready, click Activate. Existing provider authentication is reused when available.

4. Where the Kit saves things

• Downloaded adapter bundles live under <Project>/Saved/NwiroIntegrationKit/. They do not modify project content.
• Nwiro-managed Codex runtimes live in a per-user directory outside the plugin and project (on Windows, %LOCALAPPDATA%/Nwiro/IntegrationKit/runtimes/codex-acp/). Compatible global packages remain user-owned and are never modified.
• Tool-layer state is stateless between editor sessions; each conversation is new, matching how Claude Code / Codex normally work.
• No account data, no telemetry to Nwiro. Everything is between you and your AI provider.

Updating either plugin

1. Close Unreal Engine completely.
2. Open the Fab tab for the plugin and click Update.
3. Relaunch the editor.

Your local settings, account session (Pro), and any generated assets are preserved. Nwiro-managed Codex runtimes remain in their per-user directory across plugin updates.

Uninstalling

Pro

1. Close Unreal Engine.
2. Disable Nwiro in Edit → Plugins, or remove the plugin folder entirely.
3. Optionally remove Content/NwiroAssets/ if you want to clear generated PCG graphs and spline blueprints.
4. If you downloaded the demo pack and want the ~5 GB back, delete %APPDATA%/Nwiro/compressed/ and %APPDATA%/Nwiro/extracted/.

Integration Kit

1. Close Unreal Engine.
2. If you also want to remove Nwiro’s managed Codex runtime, use the managed-removal action on the Codex Integration card first. Removing it reveals a compatible global runtime as the fallback and never deletes that global package.
3. Disable or remove Nwiro Integration Kit the same way. Adapter bundles stored with the plugin are removed with it; provider-owned CLI installations and global packages are not.

Common install issues

Plugin doesn’t appear under Edit → Plugins

• The folder name must be exactly Nwiro (Pro) or NwiroIntegrationKit (Kit). Nothing nested.
• The .uplugin file must sit at the root of that folder.
• Check EngineVersion in the .uplugin matches your editor (5.5 / 5.6 / 5.7).
• On Windows, Unreal silently ignores plugins if the path is too long. Move the project closer to the drive root if you’re hitting Windows’ MAX_PATH.

“Plugin failed to load” on startup

• Pro: Web Browser, PCG Framework, and Python Editor Script Plugin all need to be enabled.
• Integration Kit: Web Browser is the only hard dependency.
• If a dependency was disabled, Unreal prints the name in the error dialog. Re-enable and restart.

Toolbar icon is missing

• Make sure the plugin is Enabled in the Plugins window.
• Restart the editor. Some toolbar icons only bind after a full relaunch.

Chat panel opens but stays blank

• Web Browser plugin is disabled or the embedded Chromium failed to initialize. Re-enable Web Browser and restart.
• On Windows, some antivirus tools block CEF from spawning. Whitelist the editor binary if you see a pattern.

“Insufficient balance” on your first Pro message

• You used up the trial prompts. Top up in Profile → Credits or subscribe. Monthly plans include bonus credits that roll over.

Adapter download / Codex managed install hangs (Integration Kit)

• For Claude, check access to the adapter’s GitHub release.
• For the official Codex runtime on Windows or macOS, confirm Node.js 20+ and npm are detected and that npm can reach its registry.
• Behind a corporate proxy, use your organization’s approved installations. The Kit reuses a compatible global official Codex runtime without modifying it.

For other issues, see Reference → Troubleshooting.

© 2026 Leartes Studios. All rights reserved.