FAQ

Does it work on macOS or Linux?

Not in this release. The shipping build declares Win64 as its only supported platform.

The POSIX PTY code path exists in the source and is maintained deliberately rather than stripped out, because cross-platform support is a planned direction — but it is compiled out of the current build.

Does it work on Unreal Engine 5.7 or earlier?

No. Conductor Terminal requires 5.8.0+, because it builds on Epic’s ModelContextProtocol and ToolsetRegistry plugins, which arrived in 5.8.

Do I need an AI agent to use it?

No. It is a fully functional terminal on its own — shells, splits, scrollback, TUI apps, inline graphics, asset links. The agent features are what it is for, but nothing forces you to use them.

Does it come with an AI agent?

No. You bring your own CLI agent and your own API access. The plugin never sees your keys, never proxies your traffic, and does not sit between your agent and its model. Your agent runs in the terminal as an ordinary process.

Will it modify my shell profile?

Never. Not .bashrc, not your PowerShell $PROFILE, not .zshrc — not even a transient, opt-in edit. This is a standing rule, not a current limitation. Nothing the plugin does persists on your machine in a way that would need uninstalling.

Why can’t the agent just run commands for me?

It already can — through its own tooling, where it also sees its own output and exit codes. A terminal-side RunCommand tool would be redundant, so it is deliberately not built. The tools that exist are the ones that let the agent take part in the surface you are both looking at: read the screen, list the panes, get your attention.

There is more on this in How the Agent Connects.

How many terminals can I open?

Four numbered tabs, plus the status-bar panel drawer, which is a host in its own right. Each can hold multiple sessions and arbitrarily nested split panes, so the practical pane count is much higher than four.

Do my terminals survive an editor restart?

The layout always does — tabs, session lists, split arrangements, tints, which session was active.

The live shells only survive in PSMux or Tmux workspace mode, where the multiplexer owns the process rather than the editor. In Plain Shell mode the shells respawn fresh. Scrollback is never written to disk.

Do I need psmux?

Only for PSMux Workspace mode. The terminal is fully functional without it. It is not bundled and the plugin will not install it; winget install marlocarlo.psmux does.

Can I use it with Cursor / Copilot / Codex / Gemini / OpenCode?

Yes — and about twenty more. See Supported Agent Targets. Anything that speaks HTTP MCP works; the target list is only about auto-configuring the agent’s config file for you.

Does the agent see everything I type?

It can read what is in a terminal pane’s buffer if it calls ReadTerminalOutput or GrepTerminalOutput on that pane — that is the point of a shared surface. It does not receive keystrokes as you type them, and it reads only the panes it asks about.

If you need to type something you would rather the agent not read, use a pane it is not looking at, or a terminal outside the editor.

What is the train horn?

The default chime for agent notifications. It ships with the plugin. You can replace it with any SoundBase asset, or silence all plugin audio with the Sound Effects master switch.

It is called Conductor Terminal. There was going to be a horn.

Can I turn the sounds off completely?

Yes. Sound Effects is a hard, structural mute — every sound the plugin plays routes through that one gate.

Where are my settings stored?

<YourProject>/Saved/Config/WindowsEditor/EditorPerProjectUserSettings.ini, per-user and per-project. That file is not normally committed, so your terminal preferences do not follow a teammate who checks out the project.

Is it a webview? Will it eat my memory?

No. There is exactly one renderer, a native Slate renderer over a real ConPTY. An earlier CEF-hosted xterm.js renderer was removed entirely — no fallback, no toggle, no Chromium in your editor process.