Support

Conductor Terminal is made by Reality Shift LLC.

Get in touch

Website — reality-shift.net
Product page — reality-shift.net/conductor-terminal
Contact — the contact form on the Reality Shift site

Before you write

A bug report with these five things in it usually gets solved in one reply. Without them it takes three.

Unreal Engine version — exact, e.g. 5.8.0
Windows build — run winver
Conductor Terminal version — Edit → Plugins → Conductor Terminal
Output Log lines — filter for LogConductorTerminal. Set the log verbosity to Verbose first if the problem is in shell detection or session startup:
```
Log LogConductorTerminal Verbose
```
What you did, what happened, what you expected — in that order, in plain sentences.

For agent-related problems, add:

which CLI agent and version
whether it lists the Cndctr Terminal toolset at all
the MCP port and path from Project Settings → Plugins → Model Context Protocol

Before that, though

Troubleshooting covers the failures that come up most: blank panes, missing tools, absent WSL distributions, asset links that don’t fire, layouts that don’t restore. It is worth two minutes.

Feature requests

Welcome — with one thing worth knowing up front about how they get judged.

Every feature is weighed against a single question: does this improve the dialogue between the human and the agent? A request that makes it easier for you to direct the agent, or for the agent to present itself to you, has a good chance. A request that would mainly make this a more complete terminal emulator will probably be declined, however sound it is technically.

Long-term maintenance is also treated as a first-class cost. Anything that creates a support treadmill — per-shell integration code, anything that rots as external tools change — is looked at sceptically even when it adds real capability.

None of which means don’t ask. It means a request framed as “here is the conversation this would make better” lands much better than a feature name.