--- title: Scheduling actions in the GitHub Copilot CLI | daily.dev description: GitHub Copilot CLI now supports scheduling prompts via two experimental commands: `/every` for recurring tasks at a set interval (minimum 10 seconds, maximum 1... canonical: https://daily.dev/posts/scheduling-actions-in-the-github-copilot-cli-coiho8fd3 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Scheduling actions in the GitHub Copilot CLI | daily.dev og:description: GitHub Copilot CLI now supports scheduling prompts via two experimental commands: `/every` for recurring tasks at a set interval (minimum 10 seconds, maximum 1... og:url: https://daily.dev/posts/scheduling-actions-in-the-github-copilot-cli-coiho8fd3 og:image: https://api.daily.dev/og/posts/coIHo8fD3.png og:image:alt: Scheduling actions in the GitHub Copilot CLI og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Scheduling actions in the GitHub Copilot CLI **[The Art of Simplicity](https://daily.dev/sources/bartwullems)** · 3 min read · 0 upvotes · 0 comments ## Summary GitHub Copilot CLI now supports scheduling prompts via two experimental commands: `/every` for recurring tasks at a set interval (minimum 10 seconds, maximum 1 day) and `/after` for one-shot delayed prompts. Both require enabling experimental mode first. Scheduled prompts are session-scoped, meaning they only run while the terminal session is active. Managing schedules includes viewing active ones, canceling by ID, and deleting via an interactive list. For persistent scheduling outside a session, users must rely on Task Scheduler, GitHub Actions, or Azure DevOps pipelines. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I schedule a recurring prompt in GitHub Copilot CLI? Use the /every command with an interval and prompt text, such as /every 10m Run the test suite and summarize any new failures. A number with no suffix is interpreted as minutes, the minimum interval is 10 seconds, and the maximum is 1 day. The command requires experimental mode enabled first via /experimental on or the --experimental flag. _Developers automating repetitive Copilot CLI checks can track feature rollouts like this on daily.dev._ ### What is the difference between /every and /after in GitHub Copilot CLI? The /every command repeats a prompt on a set interval during a session, while /after fires a prompt once after a delay and then removes it from the schedule list. Both are experimental features requiring /experimental on to enable. If an /after prompt has not triggered when the session closes, it stays queued and fires once the session reopens. _Anyone comparing scheduling approaches in Copilot CLI can follow updates on daily.dev._ ### Do scheduled prompts in GitHub Copilot CLI keep running after I close the terminal? No, scheduled prompts created with /every or /after are scoped to the session in which they were created and stop triggering once that terminal session closes. Reopening the session reactivates the schedule, but nothing runs while the session is inactive. To execute prompts without an active session, use Task Scheduler, GitHub Actions, or Azure DevOps pipelines instead. _Developers relying on unattended automation can watch for Copilot CLI updates on daily.dev._ ## Similar posts on daily.dev - [Copilot CLI: Improved UI, rubber duck, prompt scheduling, and voice input](https://daily.dev/posts/copilot-cli-improved-ui-rubber-duck-prompt-scheduling-and-voice-input-hioghuaxz) · GitHub Changelog · 0 upvotes · 0 comments - [A guide to slash commands in the GitHub Copilot app](https://daily.dev/posts/a-guide-to-slash-commands-in-the-github-copilot-app-5yktclyxl) · GitHub Blog · 0 upvotes · 0 comments - [GitHub Copilot CLI Tips & Tricks — Part 4: Automating and enforcing policies with hooks](https://daily.dev/posts/github-copilot-cli-tips-tricks-part-4-automating-and-enforcing-policies-with-hooks-ucqhydtbd) · The Art of Simplicity · 0 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#automation](https://daily.dev/tags/automation), [#cli](https://daily.dev/tags/cli) [View this post on daily.dev](https://daily.dev/posts/scheduling-actions-in-the-github-copilot-cli-coiho8fd3) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Scheduling actions in the GitHub Copilot CLI","url":"https://daily.dev/posts/scheduling-actions-in-the-github-copilot-cli-coiho8fd3","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/scheduling-actions-in-the-github-copilot-cli-coiho8fd3"},"datePublished":"2026-06-29T07:47:08.109Z","dateModified":"2026-09-14T06:47:04.197Z","description":"GitHub Copilot CLI now supports scheduling prompts via two experimental commands: `/every` for recurring tasks at a set interval (minimum 10 seconds, maximum 1...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/740091087732d27d125802bb8200dd41?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/740091087732d27d125802bb8200dd41?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"The Art of Simplicity","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"The Art of Simplicity","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/52b68c70636d44f0901ae7cd107c9438","url":"https://daily.dev/sources/bartwullems"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/scheduling-actions-in-the-github-copilot-cli-coiho8fd3","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,automation,cli","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The Art of Simplicity","item":"https://daily.dev/sources/bartwullems"},{"@type":"ListItem","position":3,"name":"Scheduling actions in the GitHub Copilot CLI"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/scheduling-actions-in-the-github-copilot-cli-coiho8fd3#faq","mainEntity":[{"@type":"Question","name":"How do I schedule a recurring prompt in GitHub Copilot CLI?","acceptedAnswer":{"@type":"Answer","text":"Use the /every command with an interval and prompt text, such as /every 10m Run the test suite and summarize any new failures. A number with no suffix is interpreted as minutes, the minimum interval is 10 seconds, and the maximum is 1 day. The command requires experimental mode enabled first via /experimental on or the --experimental flag. Developers automating repetitive Copilot CLI checks can track feature rollouts like this on daily.dev."}},{"@type":"Question","name":"What is the difference between /every and /after in GitHub Copilot CLI?","acceptedAnswer":{"@type":"Answer","text":"The /every command repeats a prompt on a set interval during a session, while /after fires a prompt once after a delay and then removes it from the schedule list. Both are experimental features requiring /experimental on to enable. If an /after prompt has not triggered when the session closes, it stays queued and fires once the session reopens. Anyone comparing scheduling approaches in Copilot CLI can follow updates on daily.dev."}},{"@type":"Question","name":"Do scheduled prompts in GitHub Copilot CLI keep running after I close the terminal?","acceptedAnswer":{"@type":"Answer","text":"No, scheduled prompts created with /every or /after are scoped to the session in which they were created and stop triggering once that terminal session closes. Reopening the session reactivates the schedule, but nothing runs while the session is inactive. To execute prompts without an active session, use Task Scheduler, GitHub Actions, or Azure DevOps pipelines instead. Developers relying on unattended automation can watch for Copilot CLI updates on daily.dev."}}]} ```