Tim - Hello đź‘‹ I am unable to get the past con...
# dev-help
t
Hello đź‘‹ I am unable to get the past conversations sidebar (or any sidebar) to show up in my spotter embed Here is my code
Copy code
<SpotterEmbed
        updatedSpotterChatPrompt
        className="h-full"
        spotterSidebarConfig={{
          enablePastConversationsSidebar: true,
          spotterSidebarTitle: 'My Conversations',
          spotterSidebarDefaultExpanded: true
        }}
        worksheetId={worksheetId}
      />
My cluster is on 26.4, visual embed sdk is on 1.47.2
a
message has been deleted
s
Thanks for sharing the code — your config is actually correct for SDK 1.47.2 + cluster 26.4. What I can confirm from the docs: -
enablePastConversationsSidebar
must be set inside
spotterSidebarConfig
(you already did this). - The standalone
enablePastConversationsSidebar
was deprecated in 1.47.0 / 26.4. -
updatedSpotterChatPrompt: true
is the right flag to enable the new Spotter chat interface. So based on official behavior, your snippet should be enough to show the chat history sidebar. ### Most likely issue in your specific snippet You’re using the React component form (
<SpotterEmbed ... />
). In React SDK wrappers, some Spotter flags can lag behind the core embed view config support depending on the wrapper build. A reliable workaround is to instantiate Spotter via the JS class directly (
new SpotterEmbed(...).render()
) and pass the same
spotterSidebarConfig
. ### Quick checks 1. Confirm the user has prior Spotter chats (empty history can look like “no sidebar” in some experiences). 2. Check browser console for embed warnings/errors. 3. Verify no parent CSS is clipping/collapsing left panel area (especially with strict width containers and overflow rules). 4. Test same config with class-based embed init to isolate React wrapper behavior. If you want, I can give you a drop-in single-file React example that keeps your current behavior but mounts Spotter using the class API so we can confirm whether this is wrapper-related.
t
yes please
ahhh nvm I figured it out. Past conversations was disabled in the cluster. 🤦‍♂️