| name | x-check |
| description | Explicitly invoked Oparax workflow for checking new queued X accounts once to determine whether they can receive DMs. Never invoke implicitly and never use for unavailable-account rechecks. |
X-check
Use only when Farzan explicitly invokes $x-check.
Perform the complete workflow inline in the current task. Never delegate it or start a subagent. Use only the Codex in-app Browser and .codex/outreach/outreach.py. Never send a message.
Open the X New message modal once and keep it open for the entire run. Never click or select a search result and never navigate into a conversation. The search result row already provides the exact handle, visible display name, and DM availability.
Run the whole queue in one task turn:
- Run
rtk python3 .codex/outreach/outreach.py batch check once. If its records array is empty, report completion.
- Claim the already-open signed-in X tab and open the New message modal once.
- In one continuous Browser JavaScript execution, loop through every returned record using the same search field. Do not use one Browser tool call per account.
- For each record, replace the search text with its exact handle and poll for an exact-handle result every 250 milliseconds for up to five seconds. Ignore similar handles.
- If the exact result is normal-bright and enabled/selectable, append
{handle, outcome: "available", display_name, first_name} to the in-memory results array without clicking it.
- If it is muted/greyed and disabled/unselectable, append
{handle, outcome: "unavailable"} without clicking it.
- If no exact result appears after five seconds, including when X still shows only loading skeletons, append
{handle, outcome: "invalid"} and continue to the next record.
- Return the complete results array from that single Browser execution, encode its JSON as base64 in the task runtime, and run
rtk python3 .codex/outreach/outreach.py apply-check-batch check <base64-payload> exactly once.
Do not create a goal, subagent, parallel worker, or per-account shell/browser loop. Do not split a complete queue into arbitrary batches.
Stop immediately without changing the current record on logout, X warning, rate limit, changed UI, closed New message modal, recipient mismatch, or any inconclusive state. Do not open LeanSpark.
Before reporting, run rtk python3 .codex/outreach/outreach.py count check. Return checked handles, resulting states, any stop reason, and that exact global remaining count. Never infer the remaining count from a vertical row in the status table.
