You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using an AI agent that is supposed to post tweets automatically, but it only generates text and logs “Saving Tweet” without ever actually publishing. I’ve verified that TWITTER_DRY_RUN=false in the .env, and the Twitter login appears to succeed, yet there’s no sign of an actual API call to post the tweet (no “Posting…” log, and nothing appears on the timeline). I’ve tried adjusting intervals (e.g., TWITTER_POLL_INTERVAL) and verified that the generated text is valid, but the agent remains stuck in a “generate/store” loop without calling the Twitter API. Any guidance on diagnosing why it never proceeds to post (or how to confirm the agent is truly attempting the Twitter API call) would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Hello @Clinksys! Welcome to the ai16z community. Thank you for opening your first issue; we appreciate your contribution. You are now a ai16z contributor!
Hello! Could you kindly share a screenshot of your terminal or try asking in the Discord server for more assistance? Without enough context, it’s a bit challenging to debug your situation. 😊
I’m using an AI agent that is supposed to post tweets automatically, but it only generates text and logs “Saving Tweet” without ever actually publishing. I’ve verified that TWITTER_DRY_RUN=false in the .env, and the Twitter login appears to succeed, yet there’s no sign of an actual API call to post the tweet (no “Posting…” log, and nothing appears on the timeline). I’ve tried adjusting intervals (e.g., TWITTER_POLL_INTERVAL) and verified that the generated text is valid, but the agent remains stuck in a “generate/store” loop without calling the Twitter API. Any guidance on diagnosing why it never proceeds to post (or how to confirm the agent is truly attempting the Twitter API call) would be greatly appreciated.
The text was updated successfully, but these errors were encountered: