An agent can edit the current Workshop state - but can an Agent directly prefill an Action for a end user without setting up each property of the action as a separate variable (can be massive for large actions) ?
Right now this isn’t something we support, but we are tracking and want to address this as soon as we have the space for it 
. What we’re thinking is offering the ability to prefill function or action tool parameters with application variables. If the values are prefilled, we won’t prompt the LLM to provide them.
Hmm, I may have mistinterpreted a bit, does this answer your question?
I have an agent output a struct for a use case, that also deals with this issue. The struct is the input of a function backed action, that unpacks the structs and passes it to the relevant properties.
The interface I designed for the user to approve this is basically unpacking the struct and formatting it in Markdown, so it’s easy to see what’s going on.
This also allows you to format and display changes quite easily, e.g.:
First name: Vincnet → Vincent
While not solving your specific issue, it is a solution to the underlying problem that I’ve found users to appreciate a lot.
I really wish actions were better, but they do not seem to have evolved much in the last 3-4 years.
#makeworkshoplookexpensive