Sentinel
Sentinel is your organization-wide view of cloud agent activity — runs in progress, recent history, and the changes agents produce. It helps teams keep automated work visible and reviewable, not silent background noise.
Think of it like a control room for cloud agents: one place to see what fired, whether it succeeded, and what to open next (logs, diff, or pull request).
Sentinel matters most when you run automations on a schedule or events, or when several people start cloud runs. It complements the per-run view in the Agents workspace with an org-level picture — similar to how Cursor shows run history on the agents dashboard, Devin surfaces activity on automations, and Factory tracks automation impact in Software Factory.
When to use Sentinel
If you only run occasional one-off cloud tasks, the Agents workspace may be enough. Sentinel earns its keep as automation and team usage grow.
In practice
You still review changes before they ship. Sentinel makes that review easier to schedule, not optional.
What you can see
Filter by last day, last week, or last month depending on whether you're responding to an incident, doing a weekly automation check, or planning capacity.
Run states
Review activity
Scan what's active
Look for runs that run longer than you expect or target repos you don't recognize. Compare against your automation list.
Open failures first
Failed runs usually fall into two buckets: environment (install, secrets, network) or task (the agent couldn't complete the instruction). Logs tell you which.
Sanity-check automation output
For each enabled automation, confirm recent runs match intent — useful output, no duplicate PRs, no changes outside the scoped repository.
Connect volume to usage
If run count jumps, check Usage. Spikes often trace to a newly enabled automation or a trigger firing more often than expected.
Like Cursor's shared agent URLs, you can send teammates to a specific run so they see the conversation, changes, and outcome — subject to your org's repository access rules.
Watch for
Sentinel is most useful alongside Usage & budgets. Visibility plus limits keeps automated spend predictable.
For admins
A short routine keeps cloud agents trustworthy at scale:
- Daily (a few minutes) — Scan the last 24 hours; address failures; confirm nothing is stuck in progress unusually long.
- Weekly — Review enabled automations: last run time, useful output, disable stale ones.
- After a spike — Pause the noisy automation, cancel in-flight runs if needed, fix trigger or prompt, test once manually, then re-enable.
If an automation fires too often, disable it first to stop new runs, cancel active ones from the Agents workspace, fix the trigger or instruction, then turn it back on after a successful manual test.