Request time agent config with nestjs

[blackmouse572]

Hi guys, my usecase is specific is unknown tools, system prompt and knowledge base at runtime. It gathers data onthe database by user's id then through factories to construct options for the agent. I didn't find these options in the documents.
I think when a user requests a controller endpoint, I can create a new VoltAgent instance and use it. But I am concerned about resource consumption since users can send a lot of requests, and construct new instance might be overwhelming

[omeraplak]

Hey @blackmouse572 ,
Great use case. You generally should NOT create a new VoltAgent instance per HTTP request.

Recommended pattern:

1. Create one long-lived Agent/VoltAgent at app startup.
2. Resolve user-specific prompt/tools/knowledge at runtime per call.

VoltAgent already supports this:

• instructions can be dynamic (function).
• tools can be dynamic (function) and you can also pass per-call tools in generateText(..., { tools }).
• Per-call userId, conversationId, and context are available, so your factories can build config from DB data at request time.
• Retriever receives operation context (userId, conversationId, context) so knowledge base can be tenant/user-specific.

Only if configurations are truly very different and heavy, use a small LRU/TTL cache of Agent instances keyed by config hash (instead of creating one every request).