Also, if somebody has an idea for the following: we use spaces as client spaces. Meaning as a consulting firm, we have spaces for some clients, that includes all the relevant data. We built agents that execute specific jobs (e.g. analysing from a marketing and sales operations perspective, SEO etc). I understand an agent can operate within or access only one space at a time. This means, we have to replicate the "horizontal" agent (e.g marketing_agent) and configure so that the marketing_agent can access client A, name it as marketing_agent_clientA, then do the same for client B, and hence have marketing_agent_clientB. If I change the prompt / logic in marketing_agent, these changes do not automatically transfer to the other client focused replica. I would have to go into each client agent and apply the changes manually. Is this correct? One way around this would obviously be to allow agents to invoke a space through the prompt or within the conversation, so that instead of the agent itself only the conversation builds thematically around the client. This capability does not exist, as far as I know. Any thoughts?
Hi Alexander. Isn't what you suggest similar to having a data-less agent, and then only attaching the relevant data from whatever space you want at Prompt time (which is supported)?
David, sure. I havent figured out a way to make the agent consider only 1 space and not e.g. Space Client 1 and our own "company space". I also dont want to attach all relevant files at prompt each time. Ideally it can be something like "Agent X use Space A and following attached documents for exeuction" (oversimplifying but hopefully you get the point. From what I understand Dust only allows one agent to be associated with one Space.
It seems ideally you'd want some kind of agent inheritance: a base agent would have the general prompt, and derived agents for each client would add the relevant space/docs. Though that would add complexity to the system. I'll let Dust experts give their thoughts on tackling this type of scenario.
