Twitter API drama: Why X banned Twitter CLI built by OpenClaw creator | Peter Steinberger

Quick Overview

Peter Steinberger explains that he had to take down his Twitter CLI tool, Bird, because X (formerly Twitter) changed its API to a pay-per-use model, forcing him to use the browser-based method, which is significantly slower and less functional for his automation needs, ultimately leading to the tool's removal due to these restrictions.

Key Points: Peter Steinberger removed his Twitter CLI tool, Bird, because X pushed a pay-per-use model for the Twitter Web API, making the previous integration obsolete. The browser-use method, which remains functional for some tasks, is considerably slower and lacks the token/time efficiency of direct API access. Steinberger notes that while browser automation is possible, it is much slower and he views the paywall/restriction as an inherent problem that discourages certain types of automation. He contrasts X's move with the prior system where he could use the internal API for faster, more reliable automation, even for tasks like checking bookmarked tweets. Steinberger suggests that if X continues to make automation slow and expensive, developers who rely on automation (like checking bookmarks or running agents) will face significant hurdles. He implies that X's strategy makes it difficult for smaller developers to create useful tools, as relying on browser automation is not a sustainable solution for high-frequency tasks. He recommends that if X's API access remains slow, agents should be built to use their own Twitter accounts rather than relying on X's limited access.

Context: This video features Peter Steinberger discussing the direct impact of X (formerly Twitter) changing its API access structure, specifically moving away from free or low-cost access to a pay-per-use model. Steinberger is the creator of the tool 'Bird' (a Twitter CLI) and 'OpenClaw' (a browser automation framework), and he details how X's policy changes forced him to discontinue support for the Twitter integration within his tools.

Detailed Analysis

Peter Steinberger explains that he had to discontinue his Twitter CLI tool, Bird, because X implemented a pay-per-use model for the Twitter Web API. He clarifies that while the browser-based method of interaction still works (as noted in his tweet shown on screen), it is significantly slower, lacks token efficiency, and is not suitable for the level of automation his tool provided. Steinberger states that making access slow is essentially taking away functionality, comparing it to having a 'bird with clipped wings.' He points out that many useful automation cases, such as checking bookmarked tweets or running agents on behalf of users, become impractical or impossible when access is slowed down to browser speeds. He suggests that if X continues this restrictive path, developers will need to adopt a zero-tolerance policy toward any AI-driven interaction that 'smells like AI' or relies heavily on scraping/slow automation, and instead, agents should use their own dedicated Twitter accounts for operations.