App Logo
x.com

Block X user

Block an X user by handle. Already-blocked accounts are reported rather than re-blocked. Returns handle, blocked, was_blocked.

Input

handle required

Target user's handle (with or without @). Blocking takes effect immediately, is visible to the target account, and cuts off your ability to see or interact with them, so confirm the exact handle with the user before running rather than inferring it from an earlier or unrelated message.

Output

handle required
blocked required
was_blocked required

already_present signal: true if already blocked before this call

verified_on_page required

true if the page was reloaded and re-inspected after the action, confirming the block is actually visible/present

account_used optional

handle of the logged-in account that performed the action, read from the account switcher UI (not assumed from input)

FAQ

Block an X user by handle. Already-blocked accounts are reported rather than re-blocked. Returns handle, blocked, was_blocked.
Required: handle.
It returns handle, blocked, was_blocked, account_used, verified_on_page.
Yes. It acts as you on x.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the x.com cookies saved by the Reduck extension.
It makes changes on x.com, like sending, posting or booking something.
Ask an AI agent connected to Reduck to run reduck/x.com/block_user, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/x.com/block_user
It is part of Reduck's official curated catalogue.

Start building not clicking