claude-code - 💡(How to fix) Fix /ultrareview fails with `firestore: not found` during seed bundle import (no remote, local-only repo) [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#60592Fetched 2026-05-20 03:54:32
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

/ultrareview consistently fails to start a remote session with a firestore: not found error during seed-bundle import. The failure happens before merge-base / diff-range computation — repeated retries, with and without arguments, all hit the same error.

Error Message

/ultrareview consistently fails to start a remote session with a firestore: not found error during seed-bundle import. The failure happens before merge-base / diff-range computation — repeated retries, with and without arguments, all hit the same error.

Error (verbatim)

Ultrareview could not start the remote session: seed bundle: seed bundle import: failed to import files: error executing request: file not found: {"code":"not_found","message":"file to import not found: error retrieving file to import: firestore: not found"} The orphan-main situation is what initially prevented merge-base from succeeding, but /ultrareview with no arguments uses the local-bundle path that shouldn't need merge-base — and the firestore: not found error suggests the bundle uploaded successfully but the server's lookup step failed afterward.

Root Cause

/ultrareview consistently fails to start a remote session with a firestore: not found error during seed-bundle import. The failure happens before merge-base / diff-range computation — repeated retries, with and without arguments, all hit the same error.

Code Example

Ultrareview could not start the remote session: seed bundle: seed bundle import: failed to import files: error executing request: file not found: {"code":"not_found","message":"file to import not found: error retrieving file to import: firestore: not found"}

---

/ultrareview              # fails
/ultrareview              # fails (retry)
/ultrareview <sha>        # fails (explicit base SHA)
RAW_BUFFERClick to expand / collapse

Summary

/ultrareview consistently fails to start a remote session with a firestore: not found error during seed-bundle import. The failure happens before merge-base / diff-range computation — repeated retries, with and without arguments, all hit the same error.

Error (verbatim)

Ultrareview could not start the remote session: seed bundle: seed bundle import: failed to import files: error executing request: file not found: {"code":"not_found","message":"file to import not found: error retrieving file to import: firestore: not found"}

Reproduction

Local-only git repo (no remote). On a branch alpha02 containing ~41 commits.

/ultrareview              # fails
/ultrareview              # fails (retry)
/ultrareview <sha>        # fails (explicit base SHA)

All four invocations produced byte-identical errors, so it isn't transient load-balancing flakiness on the storage tier.

Environment / repo shape

  • Local-only git repo, no remotes configured (git remote -v empty).
  • Two branches:
    • alpha02 — full history (~41 commits).
    • main — single orphan commit (no shared ancestor with alpha02).
  • Active branch: alpha02.

The orphan-main situation is what initially prevented merge-base from succeeding, but /ultrareview with no arguments uses the local-bundle path that shouldn't need merge-base — and the firestore: not found error suggests the bundle uploaded successfully but the server's lookup step failed afterward.

Expected

Either the seed bundle imports successfully, or the failure mode includes enough signal (e.g. retry-after, support reference id) to tell the user whether to retry or file a bug.

Actual

Hard failure on first attempt with no automatic retry; subsequent manual retries fail identically.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING