Skip to content

Follow codex to the vendor origin - #253

Open
vitramir wants to merge 1 commit into
mainfrom
fix/codex-upstream-origin
Open

Follow codex to the vendor origin#253
vitramir wants to merge 1 commit into
mainfrom
fix/codex-upstream-origin

Conversation

@vitramir

Copy link
Copy Markdown
Contributor

llm 0.5.1 changed two things this suite pinned to the old shape, so it fails against a current platform:

  • The OpenAI upstream is https://chatgpt.com, not https://chatgpt.com/backend-api/codex. The proxy appends the caller's own path and the CLI already addresses /backend-api/codex/responses, so the prefix was forwarded twice and the vendor answered 404 {"detail":"Not Found"}.
  • The attachment declares no file placeholder. auth.json's path and shape are the Codex CLI's, not OpenAI's, so agynd writes it and the LLM service carries nothing about it.

The test now asserts both: the origin, and that nothing about the CLI's file leaks back into the attachment.

The OpenAI binding no longer carries /backend-api/codex: the proxy appends the
caller's own path, and the CLI already addresses /backend-api/codex/responses,
so the prefix was forwarded twice and chatgpt.com answered 404. It also stopped
declaring auth.json -- that file's path and shape are the Codex CLI's, so agynd
writes it and the attachment says nothing about it.
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.

1 participant