# Claude Code 2.0: Massive Upgrade with Agent Loops Source: https://www.youtube.com/watch?v=OLNMrGu6DMI Recap page: https://rapidrecap.app/video/OLNMrGu6DMI Generated: 2026-03-08T14:30:54.686+00:00 --- ## Quick Overview Claude Code 2.0 introduces massive upgrades, centering on the new /loop command for session-scoped scheduled tasks within the terminal, which allows for persistent, self-improving automation tasks that survive restarts, contrasting with Cowork's cloud-based scheduling that runs in a VM sandbox. **Key Points:** - The new /loop command enables scheduling recurring tasks directly within the Claude Code terminal session, supporting intervals up to 3 days. - Desktop scheduled tasks are persistent, surviving restarts, and execute on the user's local machine, accessing local files, MCP servers, skills, git, and the terminal. - Cowork scheduled tasks run in a VM sandbox on the cloud infrastructure, best suited for non-developer tasks like email briefings, file cleanup, and using web search/plugins. - The CLI /loop command is session-scoped, meaning tasks are killed if the terminal session closes, the computer sleeps, or after a 3-day auto-expiry. - Desktop scheduled tasks follow a self-improving loop pattern: read state.json, do work, write updated state.json, allowing them to remember past runs and fix errors over time. - A key permission reality check exists across all platforms: desktop tasks stall on permission prompts, CLI needs `--dangerously-skip` permissions, and fixes often require manually allowing tools first. - The scheduling surface is mapped across two axes: Task Type (Business/Life vs. Code/DevOps) and Time Horizon (Short-lived/This session vs. Long-running/Indefinite). ![Screenshot at 00:00: The introductory slide displaying the title "Scheduled tasks" sets the context for the video's primary feature demonstration.](https://ss.rapidrecap.app/screens/OLNMrGu6DMI/00-00-00.jpg) **Context:** The video introduces significant new features for Claude Code 2.0, focusing heavily on the introduction of scheduled tasks via the `/loop` command in the terminal, contrasted with the existing cloud-based scheduling available in the Cowork tab. The core difference highlighted is execution environment: local machine for Desktop/CLI tasks versus a VM sandbox for Cowork tasks, leading to different access capabilities and use cases for each. ## Detailed Analysis The video details the new scheduling features in Claude Code 2.0, primarily focusing on the CLI command `/loop` for session-scoped scheduled tasks within the terminal, and contrasting this with the existing Cowork scheduled tasks. Desktop scheduled tasks, initiated via `/schedule` in the Desktop Code tab, run on the user's local machine and have access to local files, MCP servers, skills, git, bash, worktrees, and the terminal, making them ideal for developers (e.g., code reviews, dependency audits, PR triage). These tasks are session-scoped and will stop running if the terminal closes, the computer sleeps, or after a 3-day expiry. The Desktop tasks utilize a self-improving loop pattern involving reading and writing a `state.json` file to maintain memory between runs, allowing them to learn from past executions (e.g., fixing errors over time). Conversely, Cowork scheduled tasks run persistently in a VM sandbox in the cloud, utilizing connectors, plugins, and web search, making them better suited for non-developer tasks like summarizing emails, managing calendars, or running daily reports. The video also presents a matrix mapping task types (Business/Life vs. Code/DevOps) against time horizons (Short-lived vs. Long-running) to guide users on where to place specific tasks. Finally, a critical section addresses permission realities across all scheduling surfaces, noting that desktop tasks stall on permission prompts, CLI requires `--dangerously-skip`, and fixes often require manually granting 'always allow' permissions to tools first. ### CLI /loop (Session-Scoped) - Runs on YOUR machine - Dies on close, computer sleeps, 3-day auto-expiry, session restart - Access to local files, MCP servers, skills, git, terminal - Best for developers (Code reviews, PR triage) ### Cowork /schedule (Persistent, Cloud) - Runs in VM sandbox - Persistent - Access to connectors, plugins, web search, Gmail, Slack, Calendar - Best for non-developers (Email briefings, file cleanup, research) ### Task Mapping Axes - Task Type (Business & Life vs. Code & DevOps) vs. Time Horizon (Short-lived/This session vs. Long-running/Indefinite) - Tasks that could go either way are those depending on how long they need to run. ### Permission Reality Check - Desktop stalls on permission prompts - CLI needs `--dangerously-skip` - Fix: run manually first, 'always allow' each tool - Every surface has this problem; test manually before scheduling. ![Screenshot at 00:01: The initial list of example scheduled tasks for the Desktop environment, including daily summaries and weekly reports.](https://ss.rapidrecap.app/screens/OLNMrGu6DMI/00-00-01.jpg) ![Screenshot at 00:11: A visual comparison highlighting the difference between tasks that are similar to what OpenCLAW offers versus those that are not.](https://ss.rapidrecap.app/screens/OLNMrGu6DMI/00-00-11.jpg) ![Screenshot at 02:02: The 'Create scheduled task' dialog box in Claude Code Desktop, showing fields for Name, Description, Prompt, and Frequency.](https://ss.rapidrecap.app/screens/OLNMrGu6DMI/00-02-02.jpg) ![Screenshot at 03:40: A diagram illustrating the session-scoped nature of the CLI /loop command, showing the timeline and conditions that kill the process \(e.g., closing the terminal\).](https://ss.rapidrecap.app/screens/OLNMrGu6DMI/00-03-40.jpg)