Troubleshooting

The terminal is blank or won’t start

Check your Windows version. ConPTY requires Windows 10 build 18362 (version 1903) or later. On an older build the plugin logs a warning at startup and terminal behaviour degrades. There is no workaround short of updating Windows.

Check your default shell setting. If Default Shell (Windows) points at an executable that no longer exists, the launch fails. Clear the field to fall back to PowerShell, or fix the path. Paths with spaces need quoting:

"C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo -NoExit

Check your working directory. With the policy set to Custom and a path that is missing or unreachable, sessions revert to Project Root — but a path on a disconnected network drive can hang instead. Switch back to ProjectRoot to confirm.

Look in the Output Log. Filter for LogConductorTerminal. Shell detection logs every path it probes at Verbose.

The agent can’t see the editor

Work through these in order.

1. Is the editor running? The MCP server is in-process. No editor, no server.

2. Is ModelContextProtocol enabled? Check Edit → Plugins. The plugin’s setup panel will flag this with a Fix button.

3. Is Auto Start Server on? Project Settings → Plugins → Model Context Protocol. Without it the server waits to be started by hand.

4. Did you restart the editor after enabling a plugin? Enabling writes to the .uproject and needs a restart.

5. Did you restart the agent after writing its MCP config? Most CLI agents read MCP config only at startup.

6. Does the port match? The generated config uses the port from your MCP settings. If you changed it afterwards, rewrite the agent config.

7. Test the endpoint directly:

   curl.exe -i http://127.0.0.1:8000/mcp

   Nothing at all means the server is not listening.

The agent sees the editor but not the terminal tools

The Cndctr Terminal toolset is published through ToolsetRegistry. If Epic’s tools appear and this plugin’s do not, ToolsetRegistry is likely disabled, or ConductorTerminalMCP failed to load. Check Edit → Plugins and the Output Log for module load errors.

If no toolsets appear beyond the bare minimum, enable the AllToolsets aggregator — the setup panel has a Fix button for it.

PSMux Workspace mode isn’t available

psmux is not bundled and the plugin will not install it. Install it yourself:

winget install marlocarlo.psmux

Or get it from github.com/psmux/psmux, or use tmux inside WSL.

After installing, open a new session — detection happens at session creation, not at editor start. To confirm, ask the agent for GetDebugSummary(0) and look for psmuxResolved=1.

My WSL distributions don’t appear

• WSL detection needs Windows build 19041 (version 2004) or later.
• wsl.exe must be present in System32.
• The probe runs wsl -l -q; if that command fails or returns a non-zero exit code in a normal shell, detection will skip WSL too.
• docker-desktop distributions are filtered out deliberately — they are not interactive shells.

Clicking an asset path does nothing

You need a docked Content Browser. The Content Browser drawer cannot be synced to — the engine’s browser registry does not contain it, so a sync aimed at the drawer silently does nothing.

Dock at least one Content Browser in your layout. If none is docked, the engine may summon a brand new browser window instead of syncing an existing one.

Also worth checking: the path has to resolve to a real asset or a real folder. Paths to something that has been renamed or deleted are left as plain text on purpose — no link beats a dead link.

Font size resets every restart

This was a real bug in earlier builds, caused by settings being written to Config/Default*.ini while being read back from the per-user Saved config, which shadowed them. Settings now write and read on the same layer:

<YourProject>/Saved/Config/WindowsEditor/EditorPerProjectUserSettings.ini

If it still happens, check whether something else in your project — a build step, a version control hook, a CI script — is overwriting or reverting that file.

My layout didn’t come back

Restore runs once per editor process, at the first tab bootstrap. A few consequences:

• Closing and reopening the panel drawer within one session does not re-read saved records.
• If the editor crashed before writing its config on shutdown, the last layout was never saved.
• Terminal contents are never persisted. In Plain Shell mode the shells respawn fresh; only PSMux and Tmux workspaces bring their scrollback back with them.

Inline images show as garbled escape codes

The decoder recognises Sixel, iTerm2 OSC 1337 and Kitty APC. A tool emitting a variant it does not recognise will dump raw escape sequences. That is worth reporting — include the tool name, the exact command line, and a short capture of the output.

Still stuck?

Gather this before you get in touch:

• Unreal Engine version and Windows build number (winver)
• Conductor Terminal version (Edit → Plugins)
• The relevant LogConductorTerminal lines from the Output Log
• What you did, what happened, what you expected

Then head to Support.