# 158 Claude Code Routines Clearly Explained (and why it matters)
APR 14, 20265 MIN
# 158 Claude Code Routines Clearly Explained (and why it matters)
APR 14, 20265 MIN
Description
<p>Claude Code just dropped routines, and when I first saw the three options — routine, schedule, and loop — I had no idea when to use which. In this video, I break down all three modes in plain language and then demo building a routine from scratch using an X trend scanner I already had in my skill library. You'll see the full setup: GitHub connection, system prompt config, trigger options, and connector permissions. By the end, you'll know exactly which mode to use for any automation you want to build and how to get your first routine live.<br /><br />Links Mentioned:<br />Claude Code Routines: <a rel="noopener noreferrer nofollow" href="https://claude.ai/code/routines" target="_blank">https://claude.ai/code/routines</a><br />GitHub: <a rel="noopener noreferrer nofollow" href="https://github.com" target="_blank">https://github.com</a><br /><br />Timestamps<br />00:00 – Intro: The confusion with Claude Code's new features<br />00:20 – The three modes: routine, schedule, and loop<br />00:50 – When to use each mode (simple breakdown)<br />01:10 – Using Claude Code to find a skill to demo<br />01:45 – Selecting the X scan routine<br />02:00 – GitHub requirement for routines explained<br />02:18 – Creating a new routine at <a rel="noopener noreferrer nofollow" href="http://claude.ai/code/routines" target="_blank">claude.ai/code/routines</a><br />02:35 – Naming your routine and connecting your GitHub repo<br />02:50 – Dropping in your system prompt<br />03:05 – Setting the schedule trigger (10am Eastern daily)<br />03:20 – Configuring connectors and permission sets<br />03:40 – Running on demand and reviewing the output<br />04:10 – Full recap of all three modes<br /><br />Key Points<br /><br />* Claude Code has three automation modes — routine (runs on Anthropic's cloud, set it and forget it), schedule (needs local access, also available in Cowork), and loop (immediate execution in the CLI). Picking the wrong one means your automation won't work the way you expect.<br /><br />* Routines require a GitHub repository. You can't create one without it, so get your repo connected before you start.<br /><br />* The whole setup happens at <a rel="noopener noreferrer nofollow" href="http://claude.ai/code/routines" target="_blank">claude.ai/code/routines</a> — no coding required beyond having a system prompt in markdown format ready to paste in.<br /><br />* Routines support three trigger types: time-based schedule, GitHub event, or API call. That gives you flexibility depending on whether you want it cron-based, push-based, or fired from another system.<br /><br />* The X trend scanner ran automatically and surfaced several trending topic candidates with suggested content angles — zero manual research, just results ready to use.</p><p></p><p>FIND ME ON SOCIAL<br />X/Twitter: <a rel="noopener noreferrer nofollow" href="https://x.com/GanimCorey" target="_blank">https://x.com/GanimCorey</a><br />Instagram: <a rel="noopener noreferrer nofollow" href="https://www.instagram.com/coreyganim/" target="_blank">https://www.instagram.com/coreyganim/</a><br />LinkedIn: <a rel="noopener noreferrer nofollow" href="https://www.linkedin.com/in/coreyganim/" target="_blank">https://www.linkedin.com/in/coreyganim/</a><br /><br />FIND NICK ON SOCIAL<br />X: <a rel="noopener noreferrer nofollow" href="https://x.com/NickSpisak_" target="_blank">https://x.com/NickSpisak_</a><br />LinkedIn: <a rel="noopener noreferrer nofollow" href="https://www.linkedin.com/in/nicholasspisak/" target="_blank">https://www.linkedin.com/in/nicholasspisak/</a><br />YouTube: <a rel="noopener noreferrer nofollow" href="https://www.youtube.com/@UCusMlMDWZS0uOlhgL0M_q-A" target="_blank">https://www.youtube.com/@UCusMlMDWZS0uOlhgL0M_q-A</a></p>