Audit Mode
Record activity without immediately blocking it. This is the safer starting point for shared PCs, workstations, and machines with unfamiliar business software.
Windows AI and Automation Control Guide
How to Configure AI Agent Lock on Windows
Set up GiliSoft AI Agent Lock to monitor or block machine-driven input, automated window actions, clipboard activity, screen capture, selected processes, and command-line access while approved human work continues.
Control PlanReview activityAllow trusted workBlock automation
Start with the right control mode
A reliable rollout begins with visibility. Use Audit Mode first when you need to understand normal activity, then enable Protection Mode after trusted apps and expected actions are accounted for.
Protection Mode
Actively enforce the enabled modules and process rules. Use it after reviewing logs and adding trusted applications to the whitelist.
Whitelist and blacklist
Allow approved processes to work normally and identify applications that should be restricted. Rules make broad protection more practical on everyday PCs.
1. Review protection status on the Dashboard
Confirm the service, mode, modules, and recent activity
The Dashboard is the control summary. Use it before changing policies and again after each rollout stage.
- Open AI Agent Lock and enter the management password.
- Confirm that the protection service is running.
- Check whether the PC is in Audit Mode or Protection Mode.
- Review enabled modules, recent events, and blocked activity.
For a new deployment, turn on Audit Mode first and let normal work run long enough to produce useful logs.
Dashboard: service status, mode, enabled controls, and recent events2. Choose the protection modules
Modules: choose which automated actions and system paths to controlEnable controls that match the risk on this PC
Do not treat every machine identically. A front-desk PC, a production workstation, and a testing computer may need different combinations.
Input and window controlIntercept machine-driven input and restrict automated window actions.
Clipboard protectionControl clipboard activity and optionally clear copied content automatically.
Process and capture controlBlock selected processes and restrict screen-capture activity.
Strict system controlsRestrict system interfaces, Command Prompt, and PowerShell where tighter policy is required.
3. Build process whitelist and blacklist rules
Keep trusted applications available
Rules help distinguish approved business software from processes that should be monitored or blocked.
- Review the processes observed during Audit Mode.
- Add trusted applications and required system processes to the whitelist.
- Add unwanted automation tools or selected executables to the blacklist.
- Test each rule with the intended user account before wider deployment.
Use exact application paths and recognizable names where possible. Review a changed application after major software updates.
Rules: allow trusted processes and restrict selected applications4. Configure access and recovery settings
Settings: management password, recovery email, and unlock behaviorProtect administration without creating a recovery problem
- Set a strong management password that ordinary users do not know.
- Add a recovery email address and verify it is entered correctly.
- Choose the unlock behavior appropriate for temporary maintenance.
- Keep administrative credentials with the person responsible for policy changes.
These settings protect the control console itself and provide a practical recovery path if the password is forgotten.
5. Review intercept logs and refine the policy
Use evidence from the PC, not guesses
Realtime logs show what happened, when it happened, which process was involved, and which module handled the event.
- Filter or scan recent events after a normal work session.
- Identify blocked attempts that came from approved software.
- Whitelist trusted processes or adjust only the responsible module.
- Retest the task and confirm that unwanted automation remains restricted.
Logs: event time, process, protection module, and action resultRecommended deployment order
This sequence reduces disruption and gives administrators a clear reason for every exception.
Enable Audit Mode.
Run normal daily tasks.
Review observed processes.
Whitelist trusted software.
Enable core protection.
Add stricter controls only where needed.
AI Agent Lock FAQ
Should I start in Protection Mode?
For a new or unfamiliar PC, Audit Mode is the more practical starting point. It reveals normal activity before enforcement begins.
What should I do if a trusted app is blocked?
Find the event in Logs, confirm the process path, add the approved application to the whitelist, and test the task again.
Can I block selected applications?
Yes. Use the process blacklist for applications that should be restricted and the whitelist for trusted programs that must remain available.
Why add a recovery email?
It provides a recovery route if the management password is forgotten and helps prevent an avoidable lockout from the control console.
When should CMD and PowerShell be disabled?
Use those stricter modules on controlled endpoints where command-line access is not required by the user or approved support tools.
How do I confirm that a rule is working?
Repeat the test action, then review the Dashboard and Logs for the process, module, time, and enforcement result.
Configure AI Agent Lock with a controlled rollout
Start with Audit Mode, preserve trusted work with process rules, and then enable the protection modules that fit the Windows PC.
View GiliSoft AI Agent Lock
