Skip to content

feat(web): use Sourcebot branded logo in MCP OAuth consent screen#1062

Closed
msukkari wants to merge 3 commits intomainfrom
cursor/SOU-813-mcp-integration-sourcebot-logo-8ce1
Closed

feat(web): use Sourcebot branded logo in MCP OAuth consent screen#1062
msukkari wants to merge 3 commits intomainfrom
cursor/SOU-813-mcp-integration-sourcebot-logo-8ce1

Conversation

@msukkari
Copy link
Copy Markdown
Contributor

@msukkari msukkari commented Mar 30, 2026

Summary

Replace the generic logo_512.png with proper Sourcebot branded logos that support both dark and light mode in the MCP OAuth consent screen.

Changes

  • Update the OAuth consent screen to use sb_logo_dark_small.png and sb_logo_light_small.png instead of the generic logo_512.png
  • Dark logo is shown when the user has dark mode enabled (using hidden dark:block)
  • Light logo is shown when the user has light mode enabled (using block dark:hidden)
  • This pattern matches the existing implementation in topBar.tsx and other components

Before

The consent screen showed a generic black circle logo that doesn't match Sourcebot branding.

After

The consent screen now shows the proper Sourcebot logo, with correct variants for dark and light mode.

Testing

  • TypeScript type-checking passes
  • ESLint passes
  • Implementation follows established patterns in topBar.tsx and sourcebotLogo.tsx

Fixes SOU-813

Linear Issue: SOU-813

Open in Web Open in Cursor 

Summary by CodeRabbit

  • Changed
    • Updated the OAuth consent screen to display a Sourcebot branded logo with automatic dark/light mode support.

… OAuth consent screen

Replace generic logo_512.png with proper sb_logo_dark_small.png and sb_logo_light_small.png assets on the MCP integration OAuth consent screen.

- Shows dark logo variant in dark mode
- Shows light logo variant in light mode
- Consistent with logo usage in other parts of the app

Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 30, 2026

Walkthrough

These changes add dark/light mode support to the OAuth consent screen by replacing a single logo with two theme-specific logo images controlled by conditional Tailwind classes, and documenting this modification in the changelog.

Changes

Cohort / File(s) Summary
OAuth Consent Screen Theming
packages/web/src/app/oauth/authorize/components/consentScreen.tsx
Replaced single logo import with two theme-specific next/image components using conditional Tailwind classes (hidden dark:block for dark mode, block dark:hidden for light mode) to toggle logo visibility based on active theme.
Changelog
CHANGELOG.md
Added entry under ## [Unreleased] documenting the MCP OAuth consent screen logo update with Sourcebot branding and dark/light mode support.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: replacing a generic logo with Sourcebot branded logos supporting dark/light modes in the MCP OAuth consent screen.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/SOU-813-mcp-integration-sourcebot-logo-8ce1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

cursoragent and others added 2 commits March 30, 2026 21:43
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
@cursor cursor bot marked this pull request as ready for review April 2, 2026 17:23
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 11: Update the changelog entry "Updated MCP OAuth consent screen to use
Sourcebot branded logo with dark/light mode support.
[`#1062`](https://github.com/sourcebot-dev/sourcebot/pull/1062)" by prefixing it
with "[EE]" and correcting compound hyphenation: change "Sourcebot branded" to
"Sourcebot-branded" and hyphenate "dark/light-mode" (result: "[EE] Updated MCP
OAuth consent screen to use Sourcebot-branded logo with dark/light-mode support.
[`#1062`](...)").
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a4063a77-9d2d-4158-8cfd-d49c5cd04c83

📥 Commits

Reviewing files that changed from the base of the PR and between 9e07fcd and 0479059.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • packages/web/src/app/oauth/authorize/components/consentScreen.tsx

## [Unreleased]

### Changed
- Updated MCP OAuth consent screen to use Sourcebot branded logo with dark/light mode support. [#1062](https://github.com/sourcebot-dev/sourcebot/pull/1062)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add [EE] prefix to this changelog entry (and fix compound adjective hyphenation).

This entry appears to describe an enterprise-only OAuth/MCP change and should be prefixed with [EE]; also use “Sourcebot-branded” for grammar consistency.

✏️ Suggested edit
-- Updated MCP OAuth consent screen to use Sourcebot branded logo with dark/light mode support. [`#1062`](https://github.com/sourcebot-dev/sourcebot/pull/1062)
+- [EE] Updated MCP OAuth consent screen to use a Sourcebot-branded logo with dark/light mode support. [`#1062`](https://github.com/sourcebot-dev/sourcebot/pull/1062)

As per coding guidelines: “Prefix enterprise-only features with [EE]”.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- Updated MCP OAuth consent screen to use Sourcebot branded logo with dark/light mode support. [#1062](https://github.com/sourcebot-dev/sourcebot/pull/1062)
- [EE] Updated MCP OAuth consent screen to use a Sourcebot-branded logo with dark/light mode support. [`#1062`](https://github.com/sourcebot-dev/sourcebot/pull/1062)
🧰 Tools
🪛 LanguageTool

[grammar] ~11-~11: Use a hyphen to join words.
Context: ...CP OAuth consent screen to use Sourcebot branded logo with dark/light mode suppor...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 11, Update the changelog entry "Updated MCP OAuth
consent screen to use Sourcebot branded logo with dark/light mode support.
[`#1062`](https://github.com/sourcebot-dev/sourcebot/pull/1062)" by prefixing it
with "[EE]" and correcting compound hyphenation: change "Sourcebot branded" to
"Sourcebot-branded" and hyphenate "dark/light-mode" (result: "[EE] Updated MCP
OAuth consent screen to use Sourcebot-branded logo with dark/light-mode support.
[`#1062`](...)").

@msukkari msukkari closed this Apr 2, 2026
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.

2 participants