Feature request: show the bot's model logo next to its name in the bot list and chat header

Open
#71 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start by locating the bot list/sidebar and chat header components, then trace how each bot's selected model is stored and updated. Check whether provider logos and user settings already exist in the UI. Done means the provider is recognizable in both locations, updates after a model switch, and the optional tooltip and hide setting are addressed.

Written by the indexing model from the issue text.

Description

Summary

Show the model (provider logo) each bot is using right in the bot list and next to the bot's name, so you can tell at a glance which model a bot runs on without opening its profile.

Why

I run many bots across several subscriptions (Claude, ChatGPT/Codex, Grok, Gemini, and others). Today the only way to know which model a bot uses is to open its profile or the model picker. With a dozen or more bots, that is a lot of clicking, and it is easy to send a task to a bot on the wrong model.

Proposal

  • A small provider logo (Claude, OpenAI, Grok, Gemini, etc.) next to the bot's name in the sidebar list and in the chat header.
  • Optional tooltip on hover with the exact model name and effort level (e.g. "Claude Sonnet, medium").
  • Updates live when the bot's model is switched.
  • A setting to hide it for people who prefer a clean list.

Expected benefit

Faster routing of tasks to the right bot, fewer mistakes when bots share a similar job but run different models, and an easier way to keep an eye on which subscription is being used.

Dominant language
TypeScript
Stars
277
Forks
27
Avg merge
2h 47m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DuskBotAI/duskbot

All issues in DuskBotAI/duskbot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.