Private-repository task brief prescribed an unauthenticated HTTPS clone that cannot run

Reported (UTC): 2026-07-13 20:29

Private-repository task brief prescribed an unauthenticated HTTPS clone that cannot run non-interactively.

What was being attempted: the UrlResolver PR 680 rebase task explicitly required git clone https://github.com/CodexCoder21Organization/UrlResolver /code/workspace/UrlResolver-680 for a fresh full clone.

What went wrong: Git failed immediately with the exact error fatal: could not read Username for 'https://github.com': No such device or address. UrlResolver is private, and plain HTTPS clone did not receive credentials from the authenticated GitHub CLI session.

Impact: following the task brief literally blocks checkout before branch verification or rebase work can begin, and agents unfamiliar with the documented authentication behavior may waste time debugging credentials.

Workaround used: use gh repo clone CodexCoder21Organization/UrlResolver /code/workspace/UrlResolver-680, which injects the authenticated GitHub CLI credentials and still produces a fresh full clone.

Suggested durable fix: task generators and repository instructions should prescribe gh repo clone owner/repo destination for private organization repositories, or explicitly configure a Git credential helper before giving an HTTPS git clone command.

---

Production verification — 2026-07-17

Status: STILL EXISTS. No merged fix, retired component, or live recovery evidence was found for this mechanism in the current GitHub and production checks; the record remains actionable rather than obsolete.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.