claude-code - 💡(How to fix) Fix Cloud session uses stale .seed.bundle — repo not refreshed between sessions [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#46498Fetched 2026-04-11 06:18:42
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

Cloud sessions (claude.ai/code) clone from a cached .seed.bundle instead of a fresh GitHub clone. The bundle is not refreshed between sessions, resulting in stale code even in brand-new sessions.

Error Message

EnvironmentHEADDate
Local (WSL) + GitHub origina056b22Apr 11, 2026 02:19 KST
Cloud session (new)bc522d8Apr 8, 2026 23:46 KST

Root Cause

Cloud sessions (claude.ai/code) clone from a cached .seed.bundle instead of a fresh GitHub clone. The bundle is not refreshed between sessions, resulting in stale code even in brand-new sessions.

RAW_BUFFERClick to expand / collapse

Description

Cloud sessions (claude.ai/code) clone from a cached .seed.bundle instead of a fresh GitHub clone. The bundle is not refreshed between sessions, resulting in stale code even in brand-new sessions.

Evidence

  • git reflog in cloud session shows: clone: from /home/user/.seed.bundle
  • .git/config has no [remote "origin"] section (intentionally removed)
  • Two separate sessions created days apart had the same stale HEAD

Reproduction

  1. Push commits to a private GitHub repo from local CLI
  2. Wait any amount of time
  3. Start a new cloud session (e.g., via ultraplan or claude.ai/code)
  4. Run git log --oneline -1 — HEAD is days behind the latest push
  5. git remote -v returns empty (no remote configured)
  6. git fetch fails with "could not read Username" (no credentials)

Observed behavior

EnvironmentHEADDate
Local (WSL) + GitHub origina056b22Apr 11, 2026 02:19 KST
Cloud session (new)bc522d8Apr 8, 2026 23:46 KST

Gap: 6 commits, 3 days stale. Multiple new sessions all cloned from the same outdated bundle.

Expected behavior

Each new cloud session should reflect the latest state of origin/main at session creation time, as stated in the docs: "a fresh clone of your repository."

Environment

  • Repo: private GitHub repo
  • Local: WSL2 + Claude Code CLI
  • Cloud: claude.ai/code (ultraplan sessions)

extent analysis

TL;DR

Refresh the .seed.bundle or update the cloud session configuration to clone from the GitHub repository directly instead of using the cached bundle.

Guidance

  • Investigate the cloud session configuration to determine why it's cloning from the cached .seed.bundle instead of the GitHub repository.
  • Verify that the GitHub repository credentials are properly configured in the cloud session to allow for a fresh clone.
  • Consider updating the cloud session to use a fresh clone of the repository instead of the cached bundle, or to refresh the bundle periodically.
  • Check the documentation for claude.ai/code and ultraplan to see if there are any configuration options or settings that can be adjusted to achieve the expected behavior.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be related to the cloud session configuration and the use of a cached bundle. Without more information about the configuration and the cloud session setup, it's difficult to provide a more specific solution.

Recommendation

Apply a workaround by refreshing the .seed.bundle or updating the cloud session configuration to clone from the GitHub repository directly, as this is likely to resolve the issue of stale code in new sessions.

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

Each new cloud session should reflect the latest state of origin/main at session creation time, as stated in the docs: "a fresh clone of your repository."

Still need to ship something?

×6

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

Back to top recommendations

TRENDING