Message + Task

[SteveJamesDev]

I'm currently implementing the spec and think it's great.

I have a usecase, however, that requires message/send to respond with BOTH a message AND a task

It's a seemingly small use case on the surface, but ...

Agent A: Hello
Agent B: Hello

Agent A: Please do X
Agent B: Sure I'll get onto that <message + task>

To me, the "Sure I'll get onto that" message effectively belongs to the broader (none Task centric) context ... and the Taks then spawns as a separate (relatable) thread

This is particularly difficult to navigate if one starts to treat the User as an Client Agent (which I am)

Hope that makes sense.

Appreciate thoughts or feedback on the current spec decision.