Why autonomous operations
- Problems get caught early. Keepers scan connected accounts continuously, so drift surfaces before a routine review.
- Routine work runs itself. Scheduled tasks run recurring checks or a future one-time task without someone remembering.
- Noise becomes signal. Pulse suppresses duplicate monitoring events and ranks the clusters that remain.
- You set the boundary. Tool Permissions and the workspace mode control how an agent can use a connection tool.
Manual and Auto
CloudThinker has two workspace modes:
In a chat, open Agent settings and select Manual or Auto. The selected mode applies to every conversation in that workspace.
Tool Permissions are separate per-tool controls. In Manual mode, any connection tool set to Needs approval can pause, including a read tool. In Auto mode, catalogued reads skip the classifier and catalogued writes receive an Auto Mode decision. See Approval and Auto Mode for the decision paths.
What runs autonomously
Three surfaces run work without a live prompt. Configure each one on its own page.
Whichever surface starts the work, the workspace mode selects the gate. Manual mode uses Tool Permissions. Auto Mode uses its decision path to allow a call, request inline approval, escalate it, or deny it; Auto Mode describes those outcomes.
Stay informed
Every autonomous run is logged in the workspace. Notifications deliver findings, errors, and approval requests to Slack, Teams, or email. Review activity regularly and adjust the workspace mode or Tool Permissions when the work changes.Related
Approval
Configure per-tool permissions for Manual-mode agent actions
Auto Mode
Review classifier decisions for catalogued write calls
Tasks & Scheduling
Run an agent prompt on a recurring or future one-time schedule
Keepers
Enable autonomous monitors for cost, security, and performance drift