Connect Codex CLI to your Threads workflow

Codex CLI connects with a private, revocable key that your workspace generates as a one-time setup request. A local synthetic account-read check passed against a loopback Readyweek server; production onboarding, drafting and image upload through Codex have not been verified.

Local read verified Codex CLI · private key · setup request pasted once

Steps

Sign in, create your workspace, and connect your Threads account through Meta.
Open Your assistant, choose Codex CLI, and select Create Codex setup. Readyweek shows one setup request containing the server address and a key that is shown only once.
Paste the request into Codex. It stores the key in an environment variable and adds the Readyweek server; restart Codex, then run the first check below.

First check, before any draft

Paste this into the connected assistant. It reads permissions and changes nothing:

Use Readyweek to check my connected Threads account and permissions with threads_get_permissions. Do not draft, publish, or change anything.

What is and is not verified

Account reads: a local synthetic read with Codex CLI 0.153.4 against a loopback Readyweek server (2026-09-06). Not a production check.
Drafts and review: not recorded for Codex. The tools are the same ones other clients use.
Images: Codex can read local files, so uploads through the file bridge are possible in principle; not verified.

One key, one client

The setup request contains a key that is shown once and can be revoked from your workspace at any time. It is not your Threads credential, which Readyweek never sends to Codex.