@chia5966
I understand your concern. When you create an assistant dynamically and set a server URL, the assistant should indeed pull the prompts dynamically from your server. If you've set the server URL for your assistant and it's still using the static prompts, there might be a configuration issue.
Here's what you can check to ensure it works correctly:
1. **Server URL Configuration**: Verify that the server URL is correctly set in the assistant's settings. This can be done either through the dashboard under the "Advanced" tab or via the API during assistant creation or update.
2. **Server Response**: Ensure that your server is correctly handling requests from the assistant and returning dynamic prompts as expected. The server should be set up to receive the context and return appropriate responses.
3. **Assistant Update**: If you've updated the server URL after the assistant was created, make sure that the changes have been saved and that the assistant is indeed using the new configuration.
4. **Web Snippet**: When using the web snippet, ensure that it's configured to communicate with the dynamic assistant you've set up. It should not be hardcoded to use a specific assistant ID if you're relying on dynamic server URL fetching.
If after checking these points the issue persists, you might need to look into building a client-side solution that dynamically creates the assistant and sets the server URL as needed. However, this should not be necessary if the server URL is correctly configured and your server is responding with the dynamic prompts.
If you need further assistance with this, please let me know, and I can help guide you through the process or provide more detailed instructions.