Loyal-Young opened a new issue, #6706: URL: https://github.com/apache/rocketmq-dashboard/issues/6706
### Before Creating the Bug Report - [x] I checked open pull requests for prompt-template account scoping. - [x] Reproducible on `rocketmq-studio` at `8bbe7947`. ### Describe the Bug Custom AI prompt templates are described as personal templates, but `promptTemplates.ts` reads and writes all of them under one origin-wide `localStorage` key (`rocketmq-studio-ai-prompt-templates`). The Prompt Template modal does not pass any signed-in operator identity to the store. If operator A saves a custom template, logs out, and operator B signs in using the same browser profile, B sees and can apply or delete A's template. Templates may contain operational details or copied commands. ### Steps to Reproduce 1. Sign in as operator A and save a custom AI prompt template. 2. Sign out and sign in as operator B in the same browser profile. 3. Open the Prompt Template modal. A's custom template is listed for B. ### Expected Behavior Store custom templates separately for each signed-in operator. The legacy unscoped key can remain for deployments with authentication disabled, but it must not be loaded into a signed-in account because its original owner is unknown. ### Are You Willing to Submit a Pull Request? - [x] Yes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
