Jack - Hitting a UX gap with SpotterEmbed + Aut...
# dev-help
j
Hitting a UX gap with SpotterEmbed + Auto Mode and want to make sure I'm not missing a knob before filing a feature request. **Setup**:
worksheetId: "auto_mode", updatedSpotterChatPrompt: true
, past-conversations sidebar enabled. Auto Mode is on at the instance level. Initial load works great — picker shows "Auto Mode", Spotter discovers the Model from the prompt. After Spotter picks one (say "Worksheet A"), clicking + new chat starts a fresh conversation but pre-selects that previous Model instead of reverting to Auto. The docs do say "The default Model will be based on your last interaction with Spotter" so I'm guessing this is intentional, but it's confusing for out embedded users who are not data engineers or analysts. We'd really like new chats to default back to Auto — the whole reason we turned it on was to free users from having to pick.
a
message has been deleted
s
You’re not missing a SpotterEmbed knob for this today. What you described matches documented behavior for Auto Mode in Spotter 3: the default model follows the user’s last Spotter interaction, so a new chat can preselect the previously used model instead of returning to Auto. I could not find an official SpotterEmbed config that forces “+ new chat” to always reset back to Auto. Given current docs, your options are: 1. Treat this as expected behavior and keep Auto Mode enabled for first-load discovery. 2. File a feature request for “reset model selector to Auto on new chat” (this sounds valid for non-analyst UX). 3. If needed, reduce confusion with UI copy (for example, clarify in surrounding app text that model selection is remembered per user/session). Also, your setup details line up with current docs: -
updatedSpotterChatPrompt: true
enables the new Spotter 3 chat UI. - Sidebar behavior is controlled via
spotterSidebarConfig
(preferred over deprecated standalone flag). -
ConversationEmbed
is deprecated;
SpotterEmbed
is the right component.
m
Sorry @Jack. Just saw the message. Can you share the instance details. I will take a look and get back to you.
I am raising a fix for this. Will get it to production soon