Skip to content

Copilot device login for the CLI, on v0.60.3-vibetv.16.1 (VibeTV 167) - #23

Draft
DreamyTalesPAN wants to merge 4 commits into
base/vibetv-16.1from
codex/copilot-login-on-16.1
Draft

DreamyTalesPAN wants to merge 4 commits into
base/vibetv-16.1from
codex/copilot-login-on-16.1

Conversation

@DreamyTalesPAN

Copy link
Copy Markdown
Collaborator

Takes only the login part of #22 (config login --provider copilot --json, Mac-compatible first JSON line authorization_pending / verificationURI / userCode / expiresIn, token saved in the existing protected token store) and puts it on the pinned v0.60.3-vibetv.16.1 instead of main: 3 commits cherry-picked from #22 (c48c13d2f, c7b6aedfe, 62c70b51d), one conflict in the config.rs test module resolved by keeping both sides. Dropped from #22: the serve --request-timeout commit (already in .13+), the CI-runner commit and the unrelated Codex Desktop test-fixture change in codex_accounts/codex_desktop.rs.

Why: VibeTV issue 167 (Copilot sign-in for Windows customers). The upstream command (nesszer/Win-CodexBar d4a0ccc) is in no upstream release (newest v0.70.0 is 893 commits older) and the fork base v0.60.3 is 1582 commits behind it, so the small fork command is the smaller step.

Base branch base/vibetv-16.1 is the tag commit, so the diff shows only the login. Draft: no live sign-in yet, no release. A .17 tag is planned only after a native Windows build + test on the VibeTV bench.

@DreamyTalesPAN

Copy link
Copy Markdown
Collaborator Author

superseded by the move to upstream main (branch vibetv-on-nesszer-main-0311): nesszer/Win-CodexBar main already has config login --provider copilot (nesszer#1001, d4a0ccc), so no v0.60.3-vibetv.17 will be built from this PR. Leaving it open for now.

@DreamyTalesPAN

Copy link
Copy Markdown
Collaborator Author

superseded by the move to upstream main (branch vibetv-on-nesszer-main-0311, VibeTV-shop/vibetv pull request 394): nesszer main already ships config login --provider copilot, so no .17 release from this branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants