ElizaOS Twitter plugin
not posting? Every known cause.

Symptom 1: Eliza agent generates tweets but never publishes

This is the classic case from GitHub issue #1958: the agent composes a tweet, logs "Saving Tweet", and then... nothing. No "Posting" log line, no API call, no tweet. Issue #3693 is the same shape: the agent chats fine when you talk to it directly, but never posts autonomously. Generation and publishing are separate pipelines in Eliza, so one can succeed while the other silently does nothing.

Check these in order:

A known-good testing config for the current plugin:

TWITTER_DRY_RUN=false
TWITTER_POST_ENABLE=true
TWITTER_POST_IMMEDIATELY=true
TWITTER_POST_INTERVAL_MIN=90
TWITTER_POST_INTERVAL_MAX=180

If the agent posts with this config and stops when you restore yours, the problem was config. If it still does not post, it is auth: keep reading.

Symptom 3: repeated X login security alerts (and eventual account locks)

If your inbox fills with "New login to your X account" alerts every time the agent runs, you are hitting issue #1969: the plugin performed a full fresh login every time the post action fired, instead of reusing the session the Twitter client already held. From X's side, that is a new device from a server IP logging into your account dozens of times a day. First it alerts, then it challenges, then it locks the account.

Even with all of that, the pattern of a bot holding a user session is exactly what X's security systems exist to catch. The alerts are the system working as designed. The only structural fix is to stop logging in with credentials at all: either the official X API (which the current @elizaos/plugin-twitter uses) or a posting API that holds proper OAuth tokens for you.

Point your Eliza action at OpenTweet instead

Keep Eliza for what it is good at, generating content and deciding when to speak, and replace only the fragile posting layer. One custom action, one HTTP call, no login flow to break.

A minimal custom action that posts through OpenTweet:

import type { Action, IAgentRuntime, Memory, State, HandlerCallback } from '@elizaos/core';

export const postToX: Action = {
  name: 'POST_TO_X',
  description: 'Publish a tweet to X through the OpenTweet API',
  similes: ['TWEET', 'PUBLISH_TWEET'],
  validate: async (runtime: IAgentRuntime) => !!runtime.getSetting('OPENTWEET_API_KEY'),
  handler: async (
    runtime: IAgentRuntime,
    message: Memory,
    _state?: State,
    _options?: Record<string, unknown>,
    callback?: HandlerCallback
  ) => {
    const res = await fetch('https://opentweet.io/api/v1/posts', {
      method: 'POST',
      headers: {
        Authorization: `Bearer ${runtime.getSetting('OPENTWEET_API_KEY')}`,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({ text: message.content.text, publish_now: true }),
    });
    if (!res.ok) {
      const err = await res.json().catch(() => ({}));
      throw new Error(`OpenTweet API ${res.status}: ${err.error ?? 'request failed'}`);
    }
    await callback?.({ text: 'Posted to X.' });
    return true;
  },
  examples: [],
};

Want the agent to queue content instead of firing instantly? Send a timestamp:

{
  "text": "Scheduled by my Eliza agent.",
  "scheduled_date": "2026-07-15T15:00:00Z"
}

Set OPENTWEET_API_KEY in your .env or character secrets, register the action, and delete the Twitter login config entirely. If your setup speaks MCP, you can skip the custom action and connect the hosted server at https://mcp.opentweet.io/mcp instead, with create_tweet, create_thread, schedule_tweet and about 33 more tools. Full setup details are on the ElizaOS integration page.

Frequently asked questions