...
connecting...
--uptime
--routers
--queue
--today
Today's Progress
--/--
--% complete
7-Day Success Rate
--%
-- runs
🛡 Auth Health
--
--
Anomalies
--
detectors
Watcher Uptime
--
since restart
Providers
--
enabled
Quick Actions
Action Center
Name Tier Schedule Status Last Run CLI Duration 7d Actions
Activity Feed
Upcoming
--
--|--|--|--
↗ Open in Obsidian
Schedule
--|--|
SKILL.md
Task Files
Select a file
Click a file in the tree to view its contents.
Configuration
T1
No
Run History
DateCLIStatusDuration
CLI Chain
Manual Feedback
Briefing Reactions
Pending Operator Requests
Recent Feedback Stream
Today's Debriefs
Meeting Info
Debrief Instructions

AI Providers

Connector Auth Status

Not checked yet — click Run Check
What this screen is

Experiments reads per-task run telemetry under ~/.agents/sentinel/experiments/<task>/ (runs, success rate, sparklines, optional synthesis.md). Use it to spot flaky or regressing scheduled tasks.

If another browser or Cursor’s preview is missing tabs like this one, compare the build stamp next to the freshness dot in the header, or open /api/meta on the same host and port.

Task Experiment History
Task Runs Success Rate Trend Last Run Sparkline (last 30) Synthesis Variants
Webhook & label
Runs
Issue Status Received Processed Writes Summary
What this screen is

Shows live output from the Sentinel anomaly detectors (sentry-anomaly, shopify-anomaly, ga4-anomaly-check). Health status, baseline window, and any current WARN/CRITICAL findings are pulled straight from the per-detector state files in ~/.agents/sentinel/.

What this screen is

The shared findings bus (~/.agents/sentinel/shared-findings.jsonl) is how tasks broadcast cross-cutting observations — API changes, anomalies, auth issues, rate-limit discoveries — so downstream tasks see them on their next run.

Entries auto-expire after their ttl_hours. Use "Prune" to compact expired rows immediately.

0 live
When Source Finding Audience Consumers TTL left
What this screen is

Per-task learned memory at ~/.agents/sentinel/experiments/<task>/memory.md. Tasks can read and append to their own memory to build up long-term learned context across runs.

Pick a task below to see its memory.md, recent quality scores, and synthesis notes.

Tasks with memory or experiments
--
Run record