Introduction

Conductor Terminal is an embedded terminal for the Unreal Editor on Unreal Engine 5.8+, Windows 64-bit. It runs a genuine Windows pseudo-console (ConPTY) behind a native Slate renderer, so anything you can run in Windows Terminal runs here — including full-screen TUI applications.

But a terminal is not really what it is.

The idea

Conductor Terminal is the cab. The agent is the locomotive.

The plugin exists to be the place where you and a background AI agent talk while that agent works on your Unreal project. You start a CLI agent — Claude Code, Codex, OpenCode, Gemini CLI, Cursor Agent, whatever you use — inside a terminal pane. From there:

• You direct the work in plain language.
• The agent does the work through its own tooling, and through Epic’s MCP server it can reach into the editor itself.
• The terminal is the shared surface both of you can see, and the plugin gives the agent a set of MCP tools for operating that surface.

Everything in the plugin is judged against one question: does this improve the conversation between the human and the agent? Features that would merely make it a more complete terminal emulator do not get built.

A deliberate omission

There is no MCP tool for “run this command and tell me the exit code.” The agent already runs commands through its own tooling and already sees its own output — asking the terminal to do it would be redundant. The tools that exist are the ones that let the agent participate in the shared surface: read the screen, list the panes, get your attention.

What you get

A real terminal	ConPTY-backed, full ANSI/VT, alternate-screen TUI support, Kitty keyboard protocol, 5,000 lines of scrollback per pane.
Up to four terminal tabs	Plus a status-bar panel drawer you can flick open with Alt+F2.
Arbitrary split panes	Nested horizontal and vertical splits, each with its own shell and its own colour tint.
Every shell on the machine	PowerShell 7, Windows PowerShell, Command Prompt, Git Bash, WSL distributions, Cygwin, MSYS2 — detected automatically.
Persistent workspaces	Tabs, sessions, split layouts and tints restore after an editor restart. With psmux or tmux the live shells survive too.
Clickable asset paths	/Game/... references in terminal output become links that sync the Content Browser. Drag assets in to type their paths.
Inline graphics	Sixel, iTerm2 (OSC 1337) and Kitty image protocols, so an agent can show you a picture.
Twelve MCP tools	For the agent: split/close panes, manage sessions, send keys, read and grep the screen, read/write settings, and raise a toast.
A train horn	The default chime when the agent wants your attention. It is a locomotive-themed product and we are not sorry.

What it is not

• It is not cross-platform yet. The shipping build is Win64 only. The POSIX code path exists in the source and is maintained deliberately, because Linux and macOS support is a planned direction — but it is not in this release.
• It does not bundle an AI agent. You bring your own CLI agent and your own API access.
• It does not bundle a multiplexer. psmux and tmux are optional and installed separately; the terminal works fully without them.
• It never touches your shell profile. The plugin will not write to .bashrc, your PowerShell $PROFILE, .zshrc or anything like them — not even temporarily. Nothing persists on your machine that would need uninstalling.

Where to go next

• New here? → Installation, then Quick Start.
• Want to connect your agent? → Connecting Your CLI Agent.
• Looking for a specific setting? → Settings Reference.