Skip to content

Attach guardian rollouts to feedback uploads#15082

Open
charley-oai wants to merge 4 commits intomainfrom
ccunningham/guardian-feedback-rollouts
Open

Attach guardian rollouts to feedback uploads#15082
charley-oai wants to merge 4 commits intomainfrom
ccunningham/guardian-feedback-rollouts

Conversation

@charley-oai
Copy link
Collaborator

@charley-oai charley-oai commented Mar 18, 2026

Summary

  • add review_thread_id to guardian assessment events and surface it through guardian approval review notifications
  • resolve guardian rollout attachments from the parent rollout and include them in app-server /feedback uploads
  • update local /feedback flows in tui and tui_app_server to attach and display guardian rollout attachments too

Notes

  • cargo test -p codex-core still hits the existing unrelated tools::js_repl::tests::js_repl_imported_local_files_can_access_repl_globals failure (mktemp ... Operation not permitted).
  • cargo test -p codex-app-server still hits existing unrelated integration deadline has elapsed failures; the guardian-specific unit coverage for this change passed.

Add guardian review_thread_id plumbing so feedback can resolve the hidden guardian session rollout and attach it alongside the parent rollout in both app-server and local /feedback flows.

Co-authored-by: Codex <noreply@openai.com>
@charley-oai
Copy link
Collaborator Author

@codex review

charley-oai and others added 3 commits March 18, 2026 12:41
Keep the guardian rollout attachment plumbing for /feedback uploads, but remove the unnecessary app-server notification/schema field so the PR stays narrowly scoped.

Co-authored-by: Codex <noreply@openai.com>
Use guardian-specific naming in guardian assessment events and keep backward compatibility for older rollout JSON via a deserialization alias.

Co-authored-by: Codex <noreply@openai.com>
Use the rollout attachment helper directly and rely on its empty result for feedback uploads without logs.

Co-authored-by: Codex <noreply@openai.com>
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