[FEATURE]: Custom home screen logo (slot or setting; V1 home_logo has no V2 equivalent) #51916

Activity

1. github-actions

   assigned

   simonklee

   on Sep 28, 2026
2. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Sep 28, 2026
3. github-actions commented on Sep 28, 2026

   

   github-actionsBot

   on Sep 28, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn’t fully meet our contributing guidelines.

   What needs to be fixed:

   • This requests a new customization capability, so please use the Feature Request format: start the title with [FEATURE]: and include the required verification checkbox confirming you checked whether the feature has already been suggested.

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Feature Request: Custom Logo Configuration #12016: Requests the ability to customize or disable the OpenCode logo in the CLI/TUI.
   • Feature: customizable ASCII art / startup banner #33691: Requests configurable ASCII art/startup banner customization.

   If you believe this was flagged incorrectly, please let a maintainer know.
4. Qodevv

   changed the title [-]tui: no supported way to customize the home screen logo (V1 home_logo slot has no V2 equivalent)[/-] [+][FEATURE]: Custom home screen logo (slot or setting; V1 home_logo has no V2 equivalent)[/+] on Sep 28, 2026
5. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Sep 28, 2026
6. github-actions commented on Sep 28, 2026

   

   github-actionsBot

   on Sep 28, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for updating this issue with the Feature Request details, reproduction steps, and system information!
7. pranavsreedhar123 commented on Oct 9, 2026

   

   pranavsreedhar123

   on Oct 9, 2026

   More actions

   Hi @simonklee, following up on this request. I’ve prepared a V2 home.logo replacement slot to restore the customization previously available through V1’s home_logo, following the approach you described in #33691. I’d also like to include an independent stats.logo slot so plugins can replace or hide the logo on /stats. Both reuse the existing slot system and preserve the built-in content when no replacement is registered. The implementation is on my fork - commit, with focused tests and the full repository check passing.
   Would you approve opening a PR against v2 that closes this issue and includes both slots, or would you prefer stats.logo handled separately?
8. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed request, @Qodevv!

   To restate it: you'd like a supported way to replace, customize or hide the v2 home screen logo. That could be a home.logo plugin slot that supports replace, like the v1 home_logo slot, or a simple logo setting that takes a file path or false.

   You're right that v2 doesn't offer this today. The home route renders the built-in logo directly, without a slot around it, and the plugin slot map only exposes home.footer and home.footer.status on the home screen. That means a plugin can't replace just the logo yet. Adding a home.logo slot to the plugin API would make it possible, and this is the specific change I've suggested to the maintainers.

   Related:

   • Feature Request: Custom Logo Configuration #12016: the earlier, now closed, request for a configurable or disabled logo

   Maintainers will consider this.

   👍React with 👍1Reacted by Paul-Claudiu Orha