What is the right way to report research preview issues?

I isolated a critical issue related to the container image in the Codex research preview. I carefully constructed three experiments and created a GitHub repo to provide a reproducible demonstration. When I attempted to supply this to support, they gave me a canned response about “how important this must be to you” and suggesting I refresh my browser.

I posted the issue here as well, but since this is a critical defect in a new pre-release product, it is not surprising that the post has languished.

What is the right way to provide feedback to the relevant engineering teams?

1 Like