Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Remote run stuck, no cancel option, no visible timeout [1 comments, 2 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#45440•Fetched 2026-04-09 08:05:22
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
jbsegaljbsegal
Participants
github-actions[bot]github-actions[bot]jbsegaljbsegal
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Code Example

No messages of any sort. Code suggests you'd like to know:

⏺ The API only returns trigger config — no run status, no session ID, no timestamps
  for the current run. That's itself worth noting in the issue.

  For your bug report, here's what you have:

  - Trigger ID: trig_01DPSsbXLMaUH26y4JhVKCFx
  - Environment ID: env_01LEyM6jrQPHb9xU7MuLfGJR
  - Run started: ~20:25 UTC on 2026-04-08 (manually triggered via "Run now" in UI)
  - Original prompt: Used WebFetch tool on 4 URLs with no timeout — likely hung on a
  TCP connection to a non-resolving hostname
  - Duration: 85+ minutes with no termination
  - No cancel button in the UI
  - No run status visible via the trigger GET API — only config is returned
  - Model: claude-sonnet-4-6

  The key bugs to highlight: (1) no way to cancel a running session, (2) no hard
  timeout on CCR runs, (3) no run status/session ID exposed in the API or UI.
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?

I had an agent created and a test run started. As I type it's been running for 1hour, 10minutes. For what should've been a quick set of url checks (That code desktop later said should've been done differently...) "⏺ That's a bug/runaway session on Anthropic's end — nothing you can do from the UI. It'll eventually hit whatever hard timeout they have on CCR sessions.

Worth filing at https://github.com/anthropics/claude-code/issues — a stuck remote run with no cancel option and no visible timeout is a real gap."

Hopefully this isn't costing me tokens...

What Should Happen?

The CCR should either

  • have a kill button in the web ui
  • at least have a timeout

... it should be managable in some way

Error Messages/Logs

No messages of any sort. Code suggests you'd like to know:

⏺ The API only returns trigger config — no run status, no session ID, no timestamps
  for the current run. That's itself worth noting in the issue.

  For your bug report, here's what you have:

  - Trigger ID: trig_01DPSsbXLMaUH26y4JhVKCFx
  - Environment ID: env_01LEyM6jrQPHb9xU7MuLfGJR
  - Run started: ~20:25 UTC on 2026-04-08 (manually triggered via "Run now" in UI)
  - Original prompt: Used WebFetch tool on 4 URLs with no timeout — likely hung on a
  TCP connection to a non-resolving hostname
  - Duration: 85+ minutes with no termination
  - No cancel button in the UI
  - No run status visible via the trigger GET API — only config is returned
  - Model: claude-sonnet-4-6

  The key bugs to highlight: (1) no way to cancel a running session, (2) no hard
  timeout on CCR runs, (3) no run status/session ID exposed in the API or UI.

Steps to Reproduce

Have Code create an agent that fails. Have it then "fix" the agent that it then tells me to hit the Run now button. Then let it hang for some reason that I have no insight into while waiting to try the now fixed code.

Yes, this is a terrible How To Reproduce

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.87

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

I feel like this probably needs to be reported somewhere else(, too)?

extent analysis

TL;DR

The issue can be mitigated by implementing a timeout or cancel button for CCR sessions in the UI or API.

Guidance

  • The current implementation lacks a timeout or cancel button, leading to indefinite sessions.
  • To verify the issue, attempt to start a new run and check if it can be cancelled or times out.
  • Consider filing a feature request for adding a timeout or cancel button to the UI or API.
  • In the meantime, users can try to avoid using the "Run now" button with potentially problematic agents or prompts.

Example

No code snippet is provided as the issue is related to the UI and API design rather than a specific code implementation.

Notes

The exact solution may depend on the Anthropic API and Claude Code implementation details, which are not fully provided in the issue.

Recommendation

Apply workaround: Implement a timeout or cancel button for CCR sessions in the UI or API, as this would directly address the reported issue and provide a better user experience.

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…
#api#memory optimization#batch processing#GPU compatibility#latency issue

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] Remote run stuck, no cancel option, no visible timeout [1 comments, 2 participants]