fix(agent): ground empty remotes — unborn HEAD at the ref, not a dead clone - #610
Merged
Conversation
… clone
A zero-commit product repo is the blueprint bootstrap's normal starting
point ("an empty repo is ideal"), but grounding cloned with
`--branch <ref>`, which cannot match on a refless remote — the runtime
died at repo_clone_failed before dialing home and the session hung at
"Agent coming online" (observed live on sourceplane/nexara).
Now a failed ref-pinned clone is confirmed against the remote
(ls-remote through the same credential helper; any listing failure
keeps the original clone error), then recloned refless with the unborn
HEAD aimed at the bound ref — the first commit is born on the branch
the platform expects pushed. Task branches start unborn from unborn
history instead of failing on a start point that cannot resolve.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A zero-commit product repo is the blueprint bootstrap's normal starting
point ("an empty repo is ideal"), but grounding cloned with
--branch <ref>, which cannot match on a refless remote — the runtimedied at repo_clone_failed before dialing home and the session hung at
"Agent coming online" (observed live on sourceplane/nexara).
Now a failed ref-pinned clone is confirmed against the remote
(ls-remote through the same credential helper; any listing failure
keeps the original clone error), then recloned refless with the unborn
HEAD aimed at the bound ref — the first commit is born on the branch
the platform expects pushed. Task branches start unborn from unborn
history instead of failing on a start point that cannot resolve.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com