Issues with run_agent Feature and CSV Data Processing

·Jul 01, 2025 09:28 PM·

Hello! We've been experimenting with the run_agent feature, which is very exciting. We've noticed a limitation - if a child agent returns data in the form of a csv, the parent agent can't seem to access/process that data. Is this something you're working on?

2 comments

· Sorted by Oldest

Helen Deng
·
·
The explanation from the agent:
I can only access and process the data that is returned directly by the [child] agent or provided within this workspace. The full, untruncated CSV export (all 399 rows) is referenced in the [child agent]'s output as being available via Dust’s native CSV export feature, which is a manual download action performed by a user in the Dust interface—not something I can trigger or retrieve programmatically.
Remi
·
·
Thank you Helen! Indeed, this is one of the limitation today. I'll share your feedback with the team to help in the prioritization exercice 😊
🙏2

Helen Deng
·
·
The explanation from the agent:
I can only access and process the data that is returned directly by the [child] agent or provided within this workspace. The full, untruncated CSV export (all 399 rows) is referenced in the [child agent]'s output as being available via Dust’s native CSV export feature, which is a manual download action performed by a user in the Dust interface—not something I can trigger or retrieve programmatically.
Remi
·
·
Thank you Helen! Indeed, this is one of the limitation today. I'll share your feedback with the team to help in the prioritization exercice 😊
🙏2