feat(tui): route employee feedback follow-ups to internal link #10198
+154
−33
Conversation
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
Introduce a FeedbackAudience enum derived from the authenticated account email and thread it into the feedback follow-up view. When the account email ends with @openai.com, route users to the internal http://go/codex-feedback-internal link and suggest sharing go/codex-feedback/<thread-id> with a short problem description. External users keep the exact existing GitHub behavior, including the prepopulated bug template URL and the follow-up hint to mention the thread ID. Tests assert the external URL exactly and cover the employee routing. Testing: just fmt; cargo test -p codex-tui --lib
pakrym-oai
approved these changes
Jan 30, 2026
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
OpenAI employees were sent to the public GitHub issue flow after
/feedback, which is the wrong follow-up path internally.Mental model
After feedback upload completes, we render a follow-up link/message. That link should be audience-aware but must not change the upload pipeline itself.
Non-goals
Tradeoffs
We detect employees via the authenticated account email suffix (
@openai.com). If the email is unavailable (e.g., API key auth), we default to the external behavior.Architecture
FeedbackAudienceand thread it fromApp->ChatWidget->FeedbackNoteViewFeedbackAudience::OpenAiEmployeehttp://go/codex-feedback-internalObservability
No new telemetry; this only changes rendered follow-up instructions.
Tests
just fmtcargo test -p codex-tui --lib