If there is a way to define the context information obtained by the agent? #3310

Currently, when defining an agent, the available context options are limited to include_contents: literal ['default', 'none']. This design restricts agents to either accessing the entirety of the session's context or having no context at all.

However, in real-world development, agents often require more granular control over the context they receive. For instance, an agent might only need its own specific context within the broader session. The ability to define and utilize custom context is crucial for implementing advanced features like multi-turn dialogues, where an agent needs to recall specific information from its previous interactions without being overwhelmed by unrelated data from the entire session.

Therefore, optimizing the context handling mechanism to allow for custom context definitions is a critical improvement. This would empower developers to build more sophisticated and efficient multi-turn dialogue agents.