When a Dialog Appears
Sometimes a CAD command pops up a dialog box that waits for a button — a Vault prompt, an “update the assembly?” question, a check-out confirmation. SphereHarness notices these, handles the ones it (or you) already know the answer to, and asks you about anything unfamiliar instead of freezing.
Why this matters
A modal dialog blocks the CAD application until a button is pressed. Without help, a command that raised one would simply hang. SphereHarness watches for these dialogs while it works, so a request never silently stalls: it either deals with the dialog or comes back to you with exactly what it says and asks what to do.
What happens when one appears
A rule you saved runs first. If you have told SphereHarness how to answer a particular dialog before, it applies your choice immediately and notes what it clicked in its reply.
A few well-known dialogs are handled automatically. For example, an SW PDM check-out confirmation is confirmed so the operation proceeds. These built-in defaults are always overridden by a rule you save.
Anything else comes back to you. SphereHarness reports the dialog’s title, message and buttons and asks which to click — it will not guess on an unfamiliar dialog. Once the dialog is closed it re-checks the model, because the interrupted command finished in the background and its outcome needs confirming.
Telling SphereHarness what to do
You are always in charge. When SphereHarness asks about a dialog, just answer:
And if it is a dialog you will see again, ask it to remember:
Your standing rules are saved with your settings, take effect immediately, and always take priority over the built-in defaults. You can scope a rule to answer only a specific dialog, or tell SphereHarness to never touch a particular one and always ask you.
Dialogs that appear when nobody is looking
The desktop agent also keeps an eye out between commands: while it is working on a request, while it is starting a CAD for you, and all the time when you have switched on unattended mode (/unattended). It watches the CAD and the small helper programs a CAD starts (a migration tool, an error reporter, a licensing tool), so a prompt that pops up in one of those is not missed either.
- A dialog it knows the answer to is answered, and the chat says so — for example “Auto-answered AutoCAD ‘Drawing Recovery’ → Close”. Some answers are only given automatically in unattended mode; with unattended mode off, SphereHarness shows you the dialog instead.
- A dialog it does not know is captured — its title, message, buttons and a picture — and handed to the AI working on your request, which decides what to press (or asks you). A command that was waiting on that dialog stops waiting and says what it is waiting for, instead of timing out silently.
- When no request is running, the dialog is shown to you in the chat window and as a notification.
Example: if AutoCAD closed unexpectedly, its next start shows a Drawing Recovery notice with a single Close button. In unattended mode SphereHarness closes it and carries on (closing it throws nothing away — your backups stay available in AutoCAD’s Drawing Recovery Manager). Otherwise the AI tells you what it says and closes it.
Handy phrases
Worked example: opening a file that pops several dialogs
Opening an assembly can raise a chain of prompts — a project-scope warning, a “files missing from workspace” Vault question, an “update the assembly?” box. Ask SphereHarness to open the file and it will surface each one it does not already have an answer for. Tell it what to do (“cancel the project-scope prompt”, “yes to the update”), optionally add “and remember that,” and it works through the chain and confirms the assembly is open.
See also
- Troubleshooting & FAQ — what to try when a command seems stuck.
- Settings & Languages — where saved rules live.