From 4eb9f4d3b9d0a3dc76226e2a49d38e53e082e90b Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Wed, 4 Nov 2026 08:34:05 +0000 Subject: [PATCH] docs: use a GitHub workflow in the schedules example The schedules guide used email delivery for its example. Replace it with a daily development digest saved as a GitHub issue, and focus the introduction on developer tasks. --- content/manuals/agentic-platform/schedules.md | 38 +++++++++++-------- 1 file changed, 22 insertions(+), 16 deletions(-) diff --git a/content/manuals/agentic-platform/schedules.md b/content/manuals/agentic-platform/schedules.md index 59fd690f06..6d7e656a52 100644 --- a/content/manuals/agentic-platform/schedules.md +++ b/content/manuals/agentic-platform/schedules.md @@ -7,9 +7,9 @@ weight: 25 --- Schedules run a prompt or command in a sandbox at a recurring time. Use them -for work such as a daily Jira digest, an email summary, or a weekly dependency -review, without starting an agent manually or keeping a sandbox running -between tasks. +for recurring development work such as reviewing dependencies, triaging issues, +or summarizing pull requests, without starting an agent manually or keeping a +sandbox running between tasks. Each run creates a fresh sandbox with the kit, compute size, credentials, and tools saved in the schedule. When the task finishes, the sandbox is deleted. @@ -68,27 +68,33 @@ the command for each scheduled run, substituting the prompt you entered into the template's arguments. The image's `ENTRYPOINT` or `CMD` alone doesn't define how a scheduled prompt is passed to the agent. -## Example: Daily Jira digest +## Example: Daily repository activity digest -To prepare a daily summary of your team's work, connect an MCP server that -can search Jira and a server that can send email. These can be custom remote -servers. Authorize access to the project and mailbox the task needs, then -select both servers under **Tools**. +To prepare a daily summary of development activity, connect an MCP server +that can read GitHub pull requests and issues and create issues. Authorize +access to the repository, then select the server under **Tools**. If the +predefined servers don't provide these tools, add a custom remote server. Choose an agent kit, set the cadence to `0 9 * * 1-5`, and select your team's time zone. Use a prompt such as: ```text -Use the connected Jira tool to find issues in project EXAMPLE updated in -the past 24 hours. Summarize progress, blockers, and issues awaiting review. -Include issue keys and links. Use the connected email tool to send the digest -to team@example.com with the subject "Daily EXAMPLE digest". -If either service fails, report the error instead of inventing a summary. +Use the connected GitHub tools to review pull requests and issues in +OWNER/REPOSITORY updated in the past 24 hours. Summarize merged changes, +open pull requests awaiting review, and reported blockers. Include links +to the original pull requests and issues. +Save the summary as a GitHub issue in OWNER/REPOSITORY with the title +"Development digest: YYYY-MM-DD", using today's date. Check for an existing +issue with that title before creating one, and update it if it exists. +Exclude previous digest issues from the summary. +If a tool fails, report the error instead of inventing a summary. ``` -Replace the project and recipient with your own values. The prompt describes -the task; the connected servers must provide the corresponding search and -email tools. Test the task with **Run now** before relying on its cadence. +Replace `OWNER/REPOSITORY` with your repository. The GitHub issue preserves +the digest after the sandbox is deleted and gives your team a place to discuss +follow-up work. The connected server must provide the tools needed to read +repository activity and find, create, and update issues. Test the task with +**Run now** before relying on its cadence. ## Manage schedules and review runs