Claude Code /tasks Now Lists Scheduled Tasks, /loop Wakeups, Goals and Forks in One Count

Claude CodeView original changelog

Claude Code 2.1.329 expands the /tasks panel to show a session's scheduled tasks, /loop wakeups, its goal and the conversation's forks, and stops any of them with x after a confirmation. The task count in the header and footer now covers everything running in the background. Exiting with "Exit and stop tasks" also ends scheduled tasks so they do not fire again on resume, and most saved scheduled tasks from earlier versions need to be scheduled again in new signed-in sessions.

Key Takeaways

  • /tasks is now the single control panel for scheduled tasks, /loop wakeups, the goal and conversation forks, not only background shells.
  • Pressing x stops a row after asking, which makes cancelling a forgotten recurring prompt a one-step action.
  • The header and footer now show one combined count across shells, monitors, MCP calls, agents, workflows and scheduled tasks.
  • "Exit and stop tasks" now ends scheduled tasks so they do not fire again on resume, unless the user exits mid-response.
  • Most saved scheduled tasks from older versions need rescheduling in new signed-in sessions, though --resume of their own session still runs them.
  • A neighbouring fix stops a typo or unreadable file from wiping saved scheduled tasks.

One place for everything running in the background

Claude Code 2.1.329 turns /tasks into a fuller view of what a session is doing. Beyond background shells, the panel now lists this session's scheduled tasks, the wakeups created by /loop, the active /goal and any forks of the conversation. Pressing x on a row stops it after asking for confirmation, so a stray recurring prompt no longer has to be hunted down through separate commands.

The number shown in the /tasks header and in the footer's background count also changed. It is now a single figure covering shells, monitors, MCP calls, agents, workflows and scheduled tasks. Previously, users had to infer the total by adding several separate indicators together.

Exiting no longer leaves recurring work behind

The exit flow changed to match. Choosing "Exit and stop tasks" now ends this session's scheduled tasks so they do not run again after a resume, unless the user exits while Claude is still responding. Resuming a session with --resume still runs that session's own tasks.

What to check after upgrading

One change needs attention. In new signed-in sessions, most scheduled tasks saved by earlier versions need to be scheduled again, although --resume of their own session still runs them. Anyone relying on saved recurring prompts should confirm they still fire after the upgrade.

A related fix landed in the same release line: saving a scheduled task could previously erase the project's other saved tasks when the scheduled tasks file was unreadable, and a task with a typo in that file could be deleted the next time the file was saved.