[Bug] Does embed and upsert button make sense anymore?

[zackproser]

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

In the Pinecone vercel starter project that was the origin of this app, the workflow was:

1. Make a query to the base model because context is not available
2. Results were poorly because base model wasn't trained on the topic
3. Click embed and upsert to perform RAG in the background
4. Ask the same question
5. Now you get the correct answer due to context

However, now I'm wondering if it would make more sense to fire the same event that is wired to the Embed and Upsert button when the user changes the select toggle for the topic?

It's also super unclear to newcomers that they must click this button to get the desired behavior differences in chat output.

Expected Behavior

It should be reasonably straightforward for folks without deep experience in embeddings and RAG to use the demo and learn the difference between a RAG and Non-RAG pipeline.

Steps To Reproduce

Run the current version or visit production

Relevant log output

No response

Environment

- **OS**:
- **Language version**:
- **Pinecone client version**:

Additional Context

No response