Why autonomous operations
- Routine work runs itself. Automations run recurring checks, react to webhook calls and repository events, or run once at a future time — without someone remembering.
- Noise becomes signal. Pulse suppresses duplicate monitoring events and ranks the clusters that remain.
- You set the boundary. The workspace mode and per-tool permissions decide what an agent may do on its own, and the same rules apply to a scheduled run and a live chat alike.
- Everything is recorded. Every autonomous run keeps its conversation, so you can open any run and read exactly what the agent did.
Manual and Auto
CloudThinker has two workspace modes:
In a chat, open the approval control beside the model picker in the prompt box. It reads Manual or Auto. Select the mode you want. The selected mode applies to every conversation in that workspace, including runs that a trigger started.
What runs autonomously
Two surfaces run work without a live prompt. Configure each one on its own page.How autonomous work is bounded
Whichever surface starts the work, the workspace mode decides what happens before an agent uses a connection tool:
In Manual mode, Tool Permissions are the control: each connection tool is Always allow, Needs approval, or Never allow. In Auto mode, Auto Mode checks each write before it runs and can allow it, pause it for your approval, escalate it, or deny it — Auto Mode describes those outcomes.
A run that pauses this way shows Required Approval in the automation’s Runs view until a person decides, so autonomous work never silently waits.
Examples
- A Manual workspace with a daily cost report. An automation runs Alex’s cost summary every morning. The run only reads billing data through tools set to Always allow, so it finishes without waking anyone; the report waits in the run’s conversation and in notifications.
- An Auto workspace reacting to a repository event. A merge request lands and a repository trigger starts a run that needs to comment on the merge request. That write receives an Auto Mode decision first; if the decision pauses it, the run shows Required Approval until a person chooses Proceed or Cancel.
Stay informed
Every autonomous run is logged in the workspace, and each run’s conversation holds its full output. Notifications deliver findings, errors, and approval requests to Slack, Teams, or email. Review run history regularly and adjust the workspace mode, Tool Permissions, or the automation’s instructions when the work changes.Related
Automations
Run agent instructions on schedules, webhooks, and repository events
Approval
Configure per-tool permissions for Manual-mode agent actions
Auto Mode
Understand the decision each agent write receives in Auto
Pulse
Suppress duplicate events and surface ranked signal clusters