Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Ultraplan/Remote session timeout — lost work, no artifacts saved [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#46213•Fetched 2026-04-11 06:26:10
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
antonysastreantonysastre
Participants
antonysastreantonysastregithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3closed ×1commented ×1

Ultraplan (remote Claude Code session) ran for 90 minutes, then terminated with "no approval after 90 minutes" — no artifacts were saved, no branches created, no plan updates persisted. The session results are completely lost and inaccessible.

Root Cause

Ultraplan (remote Claude Code session) ran for 90 minutes, then terminated with "no approval after 90 minutes" — no artifacts were saved, no branches created, no plan updates persisted. The session results are completely lost and inaccessible.

RAW_BUFFERClick to expand / collapse

Bug Report

Description

Ultraplan (remote Claude Code session) ran for 90 minutes, then terminated with "no approval after 90 minutes" — no artifacts were saved, no branches created, no plan updates persisted. The session results are completely lost and inaccessible.

Steps to Reproduce

  1. From Claude Code CLI, triggered Ultraplan for a planning task
  2. Session launched on the web: Starting Claude Code on the web…
  3. After 90 minutes, CLI reported: Ultraplan terminated: no approval after 90 minutes
  4. No approval prompt was ever surfaced to the user
  5. No artifacts (branches, worktree changes, plan file updates) were persisted back to the local repo

Expected Behavior

  • Either the session should surface an approval prompt before timing out
  • Or partial results/artifacts should be saved and accessible after termination
  • At minimum, the session URL should remain accessible so insights can be retrieved

Actual Behavior

  • Session timed out silently after 90 minutes
  • Session URL returns 403 (inaccessible after termination)
  • Zero artifacts persisted — all compute time wasted
  • No way to recover any work the session produced

Impact

  • Billable compute time lost — 90 minutes of paid usage with nothing to show
  • Work disruption — user had to restart planning from scratch
  • This is a paying customer losing real money to a reliability issue

Environment

  • Platform: macOS (Darwin 25.3.0)
  • Claude Code CLI
  • Model: Claude Opus 4.6
  • Date: 2026-04-10

Suggestion

Remote sessions should either:

  1. Persist intermediate artifacts (branches, plan files) even on timeout
  2. Have a shorter timeout with a warning/extension prompt
  3. Keep session results accessible after termination for recovery

extent analysis

TL;DR

Implement a mechanism to persist intermediate artifacts or provide a warning/extension prompt before the 90-minute timeout to prevent loss of work and billable compute time.

Guidance

  • Review the Ultraplan session configuration to determine if there are any existing settings that can be adjusted to persist intermediate artifacts or provide a warning before timeout.
  • Consider implementing a shorter timeout period with a user prompt to extend the session, allowing the user to save their work or approve continuation.
  • Investigate the possibility of keeping the session URL accessible after termination to retrieve insights, even if the session itself is no longer active.
  • Evaluate the Claude Code CLI and Ultraplan documentation to ensure that the expected behavior is correctly documented and that users are aware of the potential for session timeouts.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

The solution may require modifications to the Ultraplan session management, Claude Code CLI, or the underlying infrastructure. It is essential to test any changes thoroughly to ensure that they do not introduce new issues or affect the overall user experience.

Recommendation

Apply a workaround by adjusting the session configuration to persist intermediate artifacts or provide a warning/extension prompt before the 90-minute timeout, as this approach can help mitigate the issue without requiring a full fix.

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…
#task chaining#parallel task#integration issue#index setup#retrieval 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