Chat profile description not displayed consistently depending on icon/favico configuration

[Jimmy-Newtron]

Description

There is an inconsistency in how the chat profile description is displayed on the home page depending on whether an icon is defined or not.

Steps to reproduce

1. Create a new chat profile in the application.
2. Set the required mandatory fields (name and description).
3. Do not define a custom icon (or leave it null).
4. Observe the chat profile display on the home page.
5. Then define an icon (URL-based or custom).
6. Observe again how the chat profile is displayed.

---

Actual behavior

• When no icon is defined, the description is not displayed at all.
• A favicon (or automatically generated icon) seems to be used instead of a proper icon fallback, but still no description appears.
• When an icon is defined and not null, the markdown description suddenly appears below the icon, along with the profile metadata.

This leads to inconsistent and unexpected UI behavior depending on whether the icon field is set.

---

Expected behavior

The chat profile should behave consistently:

• The description should always be displayed regardless of whether an icon is defined or not.

• If no icon is provided, the system should either:

  • Automatically fallback to a server-generated favicon/icon, or
  • Use a default placeholder icon

• But in all cases, the description visibility should not depend on icon presence.

---

Impact

• Confusing user experience
• Inconsistent UI rendering depending on configuration state
• Unexpected dependency between icon field and description rendering logic

---

Suggested improvement

• Decouple icon rendering logic from description rendering.
• Ensure description is always rendered when present.
• Optionally implement automatic favicon fallback when icon is not defined.

[dosubot]

You're correct — this is a confirmed bug in the frontend rendering logic. The issue is in frontend/src/components/chat/WelcomeScreen.tsx.

The logo memo first checks if (currentChatProfile?.icon) [1], and the markdown_description is only rendered inside that if branch [2]. When no icon is present, it falls back to rendering a generic <Logo> component with no description at all [3].

Interestingly, the header dropdown in frontend/src/components/header/ChatProfiles.tsx does not have this problem — it renders the description independently of the icon via a HoverCard.

A fix would involve restructuring the WelcomeScreen logic to render markdown_description outside the icon conditional, something like:

const logo = useMemo(() => {
  if (chatProfile && chatProfiles) {
    const currentChatProfile = chatProfiles.find(
      (cp) => cp.name === chatProfile
    );
    const icon = currentChatProfile?.icon;
    return (
      <div className="flex flex-col gap-2 mb-2 items-center">
        {icon ? (
          <img className="h-16 w-16 rounded-full" src={icon} />
        ) : (
          <Logo className="w-[200px]" />
        )}
        {currentChatProfile?.markdown_description ? (
          <Markdown>{currentChatProfile.markdown_description}</Markdown>
        ) : null}
      </div>
    );
  }
  return <Logo className="w-[200px] mb-2" />;
}, [chatProfiles, chatProfile]);

This decouples the description rendering from the icon presence while preserving the fallback to <Logo> when no icon is provided.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[sivajeetsabdakar]

hi, i’d like to work on this.

i will update WelcomeScreen.tsx so markdown_description renders independently of whether the chat profile has an icon, while preserving the existing icon/logo fallback behavior.

does this scope sound ok?

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[Jimmy-Newtron]

Any news?