[Feature Request / Question] Support for Dynamic resourceId in registerCopilotKit
Hi Mastra & CopilotKit teams,
I’m integrating CopilotKit into a multi-tenant Mastra backend and want each user to have their own
However, TypeScript throws an error:
It seems resourceId currently only accepts a static string, not a function callback based on runtime context.
My Questions is:
1. Is there a version of Mastra/CopilotKit that supports passing a function to resourceId?
2. If not, is there an official workaround for per-user resourceId in multi-tenant architectures?
3. Would defining a dynamic route like /copilotkit/:userId and setting resourceId: \user-${req.params.userId}`` be the recommended approach?
Thank you for any guidance—this would greatly improve multi-user memory separation using Mastra’s semantic recall and CopilotKit integration!
I’m integrating CopilotKit into a multi-tenant Mastra backend and want each user to have their own
resourceIduserIdHowever, TypeScript throws an error:
It seems resourceId currently only accepts a static string, not a function callback based on runtime context.
My Questions is:
1. Is there a version of Mastra/CopilotKit that supports passing a function to resourceId?
2. If not, is there an official workaround for per-user resourceId in multi-tenant architectures?
3. Would defining a dynamic route like /copilotkit/:userId and setting resourceId: \user-${req.params.userId}`` be the recommended approach?
Thank you for any guidance—this would greatly improve multi-user memory separation using Mastra’s semantic recall and CopilotKit integration!
