To be honest we should probably really just re-combine the agent builders back together and have the tools thing as an enum so we don't have to deal with this. I'll open a sep issue to solve this

If you merge main back into your branch, it should now be much easier to AgentBuilder<M, WithBuilderTools> in the config rather than using one single config.

I think at the moment it will be difficult to use tool server handles with this type currently (which means that using the WithToolServer type state variant will be impossible with extractors) because the submit tool basically needs to be guaranteed to exist, but I think this is a reasonable tradeoff for now.

Mmmmm got it, thanks for the fast response. In that case, shouldn't the toolchoice function be removed from the ExtractorBuilder? Also, for my use case I only need to enable RAG. If we enable the dynamic context function, would that be ok?

    /// Add dynamic context (RAG) to the extractor.
    ///
    /// On each prompt, `sample` documents will be retrieved from the index based on the RAG text
    /// and inserted in the request.
    pub fn dynamic_context(
        mut self,
        sample: usize,
        dynamic_context: impl VectorStoreIndexDyn + Send + Sync + 'static,
    ) -> Self {
        self.agent_builder = self.agent_builder.dynamic_context(sample, dynamic_context);
        self
    }

Mmmmm got it, thanks for the fast response. In that case, shouldn't the toolchoice function be removed from the ExtractorBuilder? Also, for my use case I only need to enable RAG. If we enable the dynamic context function, would that be ok?

    /// Add dynamic context (RAG) to the extractor.
    ///
    /// On each prompt, `sample` documents will be retrieved from the index based on the RAG text
    /// and inserted in the request.
    pub fn dynamic_context(
        mut self,
        sample: usize,
        dynamic_context: impl VectorStoreIndexDyn + Send + Sync + 'static,
    ) -> Self {
        self.agent_builder = self.agent_builder.dynamic_context(sample, dynamic_context);
        self
    }

Yeah that's fine.

moved to this #1456