Ultraplan/Remote session timeout — lost work, no artifacts saved

Resolved 💬 2 comments Opened Apr 10, 2026 by antonysastre Closed Apr 10, 2026

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

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗