feat(desktop): Implement loops ➿

[charlesvien]

Problem

Loops put recurring PostHog work on autopilot. Instead of kicking off the same agent task by hand every time, you define a loop once and it runs itself on PostHog's managed cloud infrastructure: on a schedule, when a GitHub event fires, or when your own code calls its API. This PR adds the desktop UI to create and manage them. The backend API lives in the posthog repo [companion PR].

Changes

• New top-level Loops section (Alpha-badged in the sidebar): a landing page with a prompt composer, your loops and starter templates, plus a loop detail view with run history, enable/pause and "Run now".
• The composer launches an interactive cloud loop-builder: a sandbox agent drafts the loop with you and presents it through the loops-review card, whose Create button is the only path that creates the loop. Templates and "Create manually" open the guided wizard (Prompt, When, Options, Review) with a clickable stepper.
• Triggers: schedule via a plain frequency picker (Hourly / Daily / Weekdays / Weekly / Once) that shows cron it can't represent as read-only "Custom" instead of rewriting it, GitHub events per repository, or an authenticated API endpoint.
• Attach a loop to a context: post runs to the feed, keep context.md updated and/or maintain a canvas (forces team visibility). Each context gets its own Loops tab with a scoped composer.
• Per-channel notifications (push, email, Slack), an Auto-fix pull requests toggle and model/adapter/reasoning effort behind Advanced; leaving the model unset lets the backend pick per run.
• Safety-limit rejections from the backend surface as a distinct "Safety limit reached" message with the reason instead of a generic failure.
• Hand-written @posthog/api-client loops module (CRUD, run/trigger with idempotency keys, run history, preview) until the OpenAPI client regenerates.
• New agent finish tool, gated to background cloud runs: the agent marks its task run completed or failed so the sandbox tears down instead of idling to a timeout.
• MCP apps get a lazy config resolver so cloud runs (which never open a local session) can render the loops-review card on desktop, and OAuth now requests the explicit scope list (including loop:read/loop:write and llm_gateway:read) instead of *, with a scope version bump forcing re-auth.

How did you test this?

• CI is green on the head commit: typecheck, unit-test, e2e, integration-test, visual-regression, build and quality all pass.
• 154 unit tests across the 10 new or changed test files pass locally: loop form validation and cron parsing, the builder prompt, the api-client loops module, finish tool gating and task-run updates, the mcp-apps config resolver, and the OAuth scope guards.
• Exercised the landing page, cloud loop-builder, create wizard and context attachment in the running desktop app.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

[trunk-io]

😎 Merged manually by @charlesvien - details.

[github-actions]

React Doctor found 10 issues in 6 files · 10 warnings.

10 warnings

src/features/loops/components/LoopBuilderComposer.tsx

• ⚠️src/features/loops/components/LoopBuilderComposer.tsx:61 Control missing accessible label control-has-associated-label

src/features/loops/components/LoopFallbacks.tsx

• ⚠️src/features/loops/components/LoopFallbacks.tsx:21 Multiple components in one file no-multi-comp
• ⚠️src/features/loops/components/LoopFallbacks.tsx:45 Multiple components in one file no-multi-comp

src/features/loops/components/LoopForm.tsx

• ⚠️src/features/loops/components/LoopForm.tsx:61 Large component is hard to read and change no-giant-component
• ⚠️src/features/loops/components/LoopForm.tsx:83 Event logic handled in an effect no-event-handler

src/features/loops/components/LoopTemplatesSection.tsx

• ⚠️src/features/loops/components/LoopTemplatesSection.tsx:54 Chained array iterations js-combine-iterations

src/features/loops/components/LoopTriggerEditor.tsx

• ⚠️src/features/loops/components/LoopTriggerEditor.tsx:307 Control missing accessible label control-has-associated-label
• ⚠️src/features/loops/components/LoopTriggerEditor.tsx:363 Control missing accessible label control-has-associated-label

src/features/loops/components/LoopsListView.tsx

• ⚠️src/features/loops/components/LoopsListView.tsx:46 Pure function rebuilt every render prefer-module-scope-pure-function
• ⚠️src/features/loops/components/LoopsListView.tsx:51 Pure function rebuilt every render prefer-module-scope-pure-function

_{Reviewed by React Doctor for commit 73109eb.}

[charlesvien]

@greptileai

[greptile-apps]

_{Reviews (1): Last reviewed commit: "chore(loops): remove mobile UI, desktop-..." | Re-trigger Greptile}

[posthog]

👋 Visual changes detected for this PR.

Review and approve in PostHog Visual Review

If these changes are unexpected, they may be caused by a flaky test or a broken snapshot on master. Don't approve — rerun the job or wait for a fix.

[greptile-apps]

_{Reviews (2): Last reviewed commit: "gate loop creation at the project cap" | Re-trigger Greptile}

[veria-ai]

PR overview

All previously flagged issues have been addressed. No open security concerns remain on this pull request.

Security review

No open security issues remain on this pull request.

Fixed/addressed: 2 · PR risk: 0/10

[charlesvien]

/trunk merge