Enabling physical AI at scale on Autopilot
Inspired by Fern — Enabling physical AI at scale.. Loop until the workflow is current, exceptions are owned, and human sign-off is captured where required.
Inspired by Fern
by Trooper
/loop 30m Start the "Enabling physical AI at scale on Autopilot" loop. Inspired by Fern (https://fern.bot). Goal: open work triaged, exceptions owned, and core integrations workflow current with audit trail Max iterations: 20 Between iterations run: Report open queue items, stale tasks, failed automations, and items awaiting human approval for Fern Exit when: zero open items without owner or explicit escalation, all external actions approved or sent, and systems of record current Step 1 — Capture signals: Ingest real-world actions, sensor feeds, or user sessions as raw episodes. Step 2 — Label and score: Extract structured labels with quality scores; quarantine low-confidence samples. Step 3 — Curate datasets: Dedupe, balance, and version datasets for downstream model training. Step 4 — Validate quality: Run spot checks and holdout evals before releasing a dataset batch. Step 5 — Ship to consumers: Export approved batches with lineage metadata to labs or training pipelines. ## Before you start Connect plugins: - GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs. - CRM (required) — Read accounts, deals, owners, stages, and onboarding state. - Slack (required) — Post summaries, approvals, blockers, and handoff updates. - Meta Ads (required) — Read Facebook/Instagram campaign, spend, variant, and creative performance. - Google Analytics (required) — Read traffic, conversion, product, or campaign performance signals. Attach skills: - Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition. - Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped. - CI debugging (optional) — Read failing checks, logs, and the smallest actionable root cause. - Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial. - Sales operations (optional) — Audit stale deals, owners, stages, forecast risk, and next steps. - Growth operations (optional) — Evaluate campaign performance, creative tests, CPA, and launch readiness. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.
Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.
1. Capture signals
Ingest real-world actions, sensor feeds, or user sessions as raw episodes.
2. Label and score
Extract structured labels with quality scores; quarantine low-confidence samples.
3. Curate datasets
Dedupe, balance, and version datasets for downstream model training.
4. Validate quality
Run spot checks and holdout evals before releasing a dataset batch.
5. Ship to consumers
Export approved batches with lineage metadata to labs or training pipelines.
Guardrails
Rules the agent must follow so it cannot cheat the exit condition.
- Require human approval before customer-facing sends, payments, or legal submissions unless pre-approved templates apply
- Preserve full audit trail linking source data to every automated action
- Escalate compliance, safety, or regulatory-sensitive items immediately
More Integrations loops
Inbox Triage with Approval
On an interval, classify incoming mail, draft safe replies for routine threads, and escalate anything that needs a human decision.
Morning Operator Brief
Daily interval loop that reads your calendar, open tickets, and inbox priorities, then delivers a concise operator brief with ranked actions.
Customer Onboarding Watch
Interval loop that watches new signups, runs the onboarding checklist against each account, and nudges or escalates stuck users.
