Notifications & Editor Context

Two features sit on the boundary between you and the agent. Both are on by default and both can be switched off.

Agent notifications

When the agent calls NotifyUser, a toast appears in the bottom-right of the editor with a title and an optional body line, and stays for about six seconds.

It never steals focus. No window is raised, nothing is brought to the front, there is no click action. You can keep modelling while a build runs and glance over when something lands.

Identical messages are de-duplicated for ten seconds, so an agent that calls it once per event cannot spam you. Titles are cut at 120 characters and bodies at 600.

The default chime is a train horn. It is a locomotive-themed product. You can replace it with any SoundBase asset in Notification Sound, or silence it without losing the toasts. Note that clearing the sound does not silence it — an empty value falls back to the engine’s compile-success chime. Use the Sound Effects switch to go quiet.

The two switches

Setting	Effect
Enable Agent Notifications	Off: toasts never display. The agent’s calls still succeed and return OK: ... (nothing shown) — it is told this is a preference, not a failure, so it will not retry.
Sound Effects	The master gate for every sound the plugin plays, notification chime included. Off means the plugin is structurally silent. The editor’s own Enable Editor Sounds preference is honoured too.

Leave notifications on and sound off if you want the visual cue without the horn.

Editor context

With Editor Context Injection on — the default — the plugin appends a compact snapshot of editor state to the Conductor Terminal skill whenever the agent fetches it:

• the current level
• your selected actors (up to ten, then a count)
• the last few editor errors and warnings (up to five, each line trimmed; the plugin’s own log categories are excluded so the agent cannot feed itself)

The block is omitted entirely when there is nothing to report.

The point is that you can say “why is this thing falling through the floor” and the agent already knows what this thing is. Without it, every turn starts with the agent asking what you are looking at, or guessing.

How it reaches the agent

The plugin never touches your agent’s prompt loop — the agent is an ordinary process and the terminal does not sit between it and its model. The snapshot rides along with the skill text that Epic’s registry hands back from its GetSkills tool. So the agent sees it when it reads the skill, typically once at the start of a session, and again whenever it chooses to re-read it. It is not injected on every turn, and it does not add to your per-turn token cost.

Turn it off if you would rather the agent only learn about the editor by asking Epic’s tools directly, or if you mostly use the terminal for work that has nothing to do with what is selected in the viewport.