docs: add trigger configuration for local agents

[continue]

Updates docs for continuedev/remote-config-server#3117

That PR added support for the on: frontmatter key in agent markdown files, allowing users to declare automated triggers (cron, GitHub events, Sentry, Snyk, Slack, webhook) directly in source control.

Changes:

• Added on field to the Frontmatter Options table in /docs/guides/run-agents-locally.mdx
• Added new "Trigger Configuration" section documenting all supported trigger types
• Included examples for GitHub events, cron schedules, and multiple triggers

Notes:

• Agents without an on: key default to triggering on GitHub PR opened events (backward compatible)
• Each trigger type in the on: config creates a separate workflow

---

Continue Tasks: ▶️ 2 queued — View all

---

Summary by cubic

Documents the new on: frontmatter for local agents so users can set automated triggers in agent markdown. Updates the Run Agents Locally guide with trigger types, examples, defaults, and workflow behavior to match remote-config-server#3117.

• New Features
  • Added on field to the Frontmatter Options table in /docs/guides/run-agents-locally.mdx.
  • New Trigger Configuration section covering GitHub events, cron, Sentry, Snyk, Slack, and webhook, with examples.
  • Documented defaults (triggers on PR opened if on is missing) and that each trigger type creates a separate workflow.

^{Written for commit a3824a8. Summary will update on new commits.}

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

root seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="docs/guides/run-agents-locally.mdx">

<violation number="1" location="docs/guides/run-agents-locally.mdx:141">
P2: `pull_request` does not emit a `merged` activity type. Merged PRs arrive as `pull_request` with action `closed` and `pull_request.merged == true`, so this example won’t match real GitHub events.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: pull_request does not emit a merged activity type. Merged PRs arrive as pull_request with action closed and pull_request.merged == true, so this example won’t match real GitHub events.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/guides/run-agents-locally.mdx, line 141:

<comment>`pull_request` does not emit a `merged` activity type. Merged PRs arrive as `pull_request` with action `closed` and `pull_request.merged == true`, so this example won’t match real GitHub events.</comment>

<file context>
@@ -86,13 +86,97 @@ Agent files are markdown documents with YAML frontmatter. The frontmatter config
+| Event | Configuration |
+|-------|---------------|
+| PR opened | `pull_request: { types: [opened] }` |
+| PR merged | `pull_request: { types: [merged] }` |
+| Issue opened | `issues: { types: [opened] }` |
+| Issue labeled | `issues: { types: [labeled] }` |
</file context>

Suggested change

	| PR merged | `pull_request: { types: [merged] }` |
	| PR merged | `pull_request: { types: [closed] }` |