claude-code - 💡(How to fix) Fix [BUG] Routines: no way to stop/cancel a running scheduled session [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56074Fetched 2026-05-05 05:58:51
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Error Message

Error Messages/Logs

Code Example

n.a.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Problem

When a scheduled Routine run gets stuck or runs unexpectedly long, there is no way to kill it — neither from the Routines UI (no Stop/Cancel button on a running run) nor programmatically (TaskStop only works for tasks spawned within the current session).

Current behavior

  • The Routines UI shows the run as active but offers no cancel action.
  • TaskStop requires a task_id that is not exposed for remote scheduled sessions.
  • The run from May 1 has been stuck for 3+ days with no way to terminate it.

Expected behavior

  • A Stop / Cancel button on any active run in the Routines UI.
  • Or: expose the task_id of a running routine session so it can be stopped via TaskStop.

Environment

  • Claude Code desktop app / Routines feature
  • OS: Windows 11 Pro

What Should Happen?

There should be an option to kill a running routine.

Error Messages/Logs

n.a.

Steps to Reproduce

Hard to reproduce. This was caused while setting up my first routine.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Claude 1.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

<img width="1917" height="1090" alt="Image" src="https://github.com/user-attachments/assets/d8fe69af-87eb-4fb2-b935-2f62394e95fd" />

extent analysis

TL;DR

To address the issue of a stuck routine run, consider modifying the Routines UI to include a Stop/Cancel button for active runs or expose the task_id of running routine sessions to enable programmatic termination via TaskStop.

Guidance

  • Investigate the feasibility of adding a Stop/Cancel button to the Routines UI for active runs to provide a straightforward way to terminate stuck or unexpectedly long-running routines.
  • Explore the possibility of exposing the task_id of running routine sessions, allowing users to stop them programmatically using TaskStop, even for sessions not spawned within the current session.
  • Review the current implementation of TaskStop to understand why it only works for tasks within the current session and assess potential modifications to extend its functionality.
  • Consider the security implications of exposing task_ids for remote scheduled sessions to ensure that any solution does not introduce vulnerabilities.

Example

No specific code example can be provided without more details on the internal implementation of the Routines UI and TaskStop functionality. However, the solution likely involves modifying the UI to include a cancellation button or adjusting the TaskStop API to accept task_ids from any session.

Notes

The provided information does not specify the technical details of how routines are managed internally, which limits the ability to provide a precise fix. The solution may require changes to the Claude Code application's backend or UI, depending on the existing architecture.

Recommendation

Apply a workaround by modifying the Routines UI to include a Stop/Cancel button for active runs, as this seems to be a more straightforward approach to provide users with a way to terminate stuck routines without requiring significant changes to the underlying task management system.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • A Stop / Cancel button on any active run in the Routines UI.
  • Or: expose the task_id of a running routine session so it can be stopped via TaskStop.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Routines: no way to stop/cancel a running scheduled session [1 participants]