It would be great to have some way to differentiate between actions and the main structure when using Stream

[shhlife]

When using structures as tools, the subtask artifacts come out the same as the main structure artifacts. It'd be handy to have some way to identify them - maybe with json, or some sort of prepending? Or something in the event bus? Otherwise it's difficult for the dev to send the right information to the user.

from griptape.structures import Agent
from griptape.utils import Stream
from griptape.tools import StructureRunTool
from griptape.drivers.structure_run.local import LocalStructureRunDriver
from griptape.rules import Rule
import logging

logger = logging.getLogger("griptape")
logger.setLevel(logging.ERROR)
def build_agent() -> Agent:
    return Agent( rules=[Rule(f"The assistant identifies as Tom")], stream=True)

agent = Agent(tools=[
    StructureRunTool(
        name="Tom", 
        description="Assistant you can talk to",
        structure_run_driver=LocalStructureRunDriver(create_structure=build_agent))], stream=True)

for artifact in Stream(agent).run("Can you ask Tom how he is doing?"):
    print(artifact.value, end="", flush=True)

I get:

    Tom.call_kmLkzq2aeNmJPD5wA5agr1Be (run_structure){
  "values": {
    "args": [
      "How are you doing?"
    ]
  }
}
I'm just a virtual assistant, so I don't have feelings, but I'm here and ready to help you! How can I assist you today?
Tom says he's just a virtual assistant, so he doesn't have feelings, but he's ready to help you. How can he assist you today?

Would love to easily be able to return something like:

(Calling run_structure Tom. "How are you doing")
(Tom): I'm just a virtual assistant, so I don't have feelings, but I'm here and ready to help you! How can I assist you today?
Tom says he's just a virtual assistant, so he doesn't have feelings, but he's ready to help you. How can he assist you today?

or something even better. :)

[collindutter]

This totally falls apart if you have multiple parallel Structures, but StartStructureRunEvent contains structure_id so you can assume all events in-between that and FinishStructureRunEvent are for that Structure.

Long term we need to add more detailed trace information to all events.