Confusing usage of RuntimeContext in workflowRoute and chatRoute
I was just using the RuntimeContext to store additional info from within a Middleware as described here.
But when using workflowRoute, the additional info was missing in the RuntimeContext.
I looked at the sources and noticed that in workflowRoute, the RuntimeContext is not explicitly extracted anywhere. It is just passed from the request body as part of the rest parameters.
I compared this with the chatRoute and found that there the RuntimeContext is explicitly extracted from the Hono context. But it doesn't seem to be supported through the request body.
Maybe I'm missing something, but I expected all these configuration points to be supported and rather be merged if there are no conflicting keys. That way some params could be provided via the request body and others can be provided through the middleware.
But when using workflowRoute, the additional info was missing in the RuntimeContext.
I looked at the sources and noticed that in workflowRoute, the RuntimeContext is not explicitly extracted anywhere. It is just passed from the request body as part of the rest parameters.
I compared this with the chatRoute and found that there the RuntimeContext is explicitly extracted from the Hono context. But it doesn't seem to be supported through the request body.
Maybe I'm missing something, but I expected all these configuration points to be supported and rather be merged if there are no conflicting keys. That way some params could be provided via the request body and others can be provided through the middleware.
Learn how Mastra leverages the Vercel AI SDK library and how you can leverage it further with Mastra
GitHub
The TypeScript AI agent framework. 
Assistants, RAG, observability. Supports any LLM: GPT-4, Claude, Gemini, Llama. - mastra-ai/mastra
Assistants, RAG, observability. Supports any LLM: GPT-4, Claude, Gemini, Llama. - mastra-ai/mastra