Check that it worked

Three places to look, in the order that answers the question fastest.

On the machine

The tool's card in the Endpoint Suite says routed through Sentilai rather than detected. If it still says detected, the connect step did not complete.

If you use VS Code, the Sentilai companion extension's status bar shows Sentilai: n/m — how many detected tools are governed.

In the tool

Send any prompt. It should behave exactly as before. If it now returns a provider error, the usual cause is managed mode without a matching provider key — see A tool stopped working after connecting.

In the console

Activity, in the admin console, gets a new row within a few seconds: the developer, the tool, the model, the outcome. That row is the proof.

If the tool works but nothing appears in Activity, it is almost always the restart: the tool is still running with its old configuration. Fully quit it and try again.

If the device shows as non-compliant

The console's Diagnostics screen can show a Non-compliant badge on a device. It means a governed tool on that machine no longer points at Sentilai — usually because somebody edited the tool's configuration by hand, or the tool rewrote it.

With automatic governing on, the app repairs this by itself on its next sweep. If it keeps coming back, something on the machine is rewriting the configuration and it is worth finding out what.