Second Tweet from Agent Replies to User Instead of Initial Agent Tweet

[KennethAshley]

Describe the bug
When the agent initiates an action (i.e. GENERATE_VIDEO), it sends two tweets:

1. An initial tweet indicating the action has started.
2. A second tweet with the payload once the action completes.

However, the second tweet (with the payload) replies directly to the user’s original tweet instead of replying to the agent’s initial tweet. This disrupts the expected reply chain and makes the interaction unclear.

To Reproduce

1. Post a tweet to the agent requesting something (e.g., “generate a video of a butterfly”).
2. Observe the agent’s initial tweet acknowledging the action initiation.
3. Wait for the video generation process to complete.
4. Observe the agent’s second tweet with the payload replying to the user’s original tweet instead of the agent’s initial tweet.

Expected behavior
The second tweet (containing the payload) should reply to the agent’s initial tweet, maintaining a logical and consistent reply chain.

Additional context

• The issue may stem from how the framework handles inReplyToId or how the initial tweet ID is stored/passed to the second tweet.
• A potential fix might involve explicitly capturing the agent’s initial tweet ID and ensuring it is passed as inReplyToId when sending the second tweet.

Let me know if you need further adjustments! 🚀

[github-actions]

Hello @KennethAshley! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor!

[tcm390]

fixed in #2966