fix(designerv2): Not passing obo token to the chat iframe

[Eric-B-Wu]

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

Fixes an issue where we aren't calling our iframe with the obo token, so chats will fail if required

Also fixes issues in standalone where we weren't fetching the obo token properly
Cherry pick of #8604

Impact of Change

• Users: Users should now be able to use agent chats that require obo tokens
• Developers: standalone changes to properly fetch the obo token
• System: no system changes

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:

Contributors

@Eric-B-Wu

Screenshots/Videos

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: fix(designerv2): Not passing obo token to the chat iframe
• Issue: The title is concise and descriptive, specifying the affected module (designerv2) and the nature of the fix (obo token handling).
• Recommendation: No changes needed. Good title format for traceability.

---

✅ Commit Type

• Properly selected (fix)
• Only one selected, which is correct

---

✅ Risk Level

• Low risk clearly selected and matches the label (Risk:Low)

---

✅ What & Why

• Current:

  Fixes an issue where we aren't calling our iframe with the obo token, so chats will fail if required

  Also fixes issues in standalone where we weren't fetching the obo token properly
  Cherry pick of fix(designerv2): Not passing obo token to the chat iframe #8604

• Issue: Clear, direct, and gives technical context and reason for the change.
• Recommendation: No changes needed.

---

✅ Impact of Change

• Clear impacts described:
  • Users: Users should now be able to use agent chats that require obo tokens
  • Developers: Standalone changes to properly fetch the obo token
  • System: No system changes
• Recommendation: No changes needed.

---

✅ Test Plan

• Manual testing completed is selected and appropriate for this bug fix.

---

⚠️ Contributors

• Only the PR author is mentioned. If other PMs, designers or team members contributed, consider tagging them for credit. Not required, so passes.

---

✅ Screenshots/Videos

• Section left blank, which is acceptable for a backend/token fix.

---

Summary Table

Section	Status	Recommendation
Title	✅
Commit Type	✅
Risk Level	✅
What & Why	✅
Impact of Change	✅
Test Plan	✅
Contributors	⚠️	Tag others if applicable for credit
Screenshots/Videos	✅

---

All required sections are correct and complete. Please consider tagging any contributors if relevant. Thank you for maintaining high PR hygiene!

---

Last updated: Thu, 20 Nov 2025 21:07:39 GMT

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: fix(designerv2): Not passing obo token to the chat iframe
• Issue: Title is concise, specific, and follows the conventional commit format.
• Recommendation: No changes needed.

---

✅ Commit Type

• Properly selected (fix)
• Only one selected, which is correct.

---

✅ Risk Level

• Correctly marked as Low risk both in the template and label. Matches the described scope and code diff size.

---

✅ What & Why

• Current:
  Fixes an issue where we aren't calling our iframe with the obo token, so chats will fail if required

  Also fixes issues in standalone where we weren't fetching the obo token properly
  Cherry pick of fix(designerv2): Not passing obo token to the chat iframe #8604

• Issue: Clear explanation provided.

• Recommendation: No improvement needed; context is sufficient.

---

✅ Impact of Change

• Impact described for Users, Developers, and System. Users and developer impact are clear; system impact confirmed as no effect.
• Recommendation: No changes needed, all sections addressed.

---

✅ Test Plan

• Manual testing completed marked appropriately, given the change scope. No additional requirements.

---

⚠️ Contributors

• Only the author listed (@Eric-B-Wu). It's always good to give additional credit to PMs, designers, or collaborators. Consider tagging collaborators if applicable.

---

✅ Screenshots/Videos

• No visual/UI changes evident from the description or title, so absence here is appropriate.

---

Summary Table

Section	Status	Recommendation
Title	✅
Commit Type	✅
Risk Level	✅
What & Why	✅
Impact of Change	✅
Test Plan	✅
Contributors	⚠️	Consider tagging teammates, PMs, designers
Screenshots/Videos	✅

---

PR body and title are both well-structured and compliant. Please consider crediting all contributors for transparency and team recognition. Otherwise, no changes needed—thank you for a high-quality submission!

---

Last updated: Thu, 20 Nov 2025 21:07:39 GMT