Claude Desktop connects through a custom connector with browser sign-in. Claude Code
connects with a private key from a one-time setup request. They are different environments with
different evidence.
Claude Desktop
Not yet verified
Custom connector · browser sign-in · no key to copy
Sign in to Readyweek, create your workspace, and connect Threads. Open Your assistant and copy the server address.
In Claude, open Customize, then Connectors, select Add custom connector, and paste the address.
Select Add, then Connect, and approve the Readyweek workspace and Threads account in your browser. If your organization manages connectors, an owner may need to add Readyweek first.
The Readyweek owner has reported drafting, review and publishing a post with an image through Claude, without recording which Claude surface was used. That is a reported result on one account, not an independent test of this environment, and it does not show agent image upload: the image was already in Readyweek.
Claude Code
Local read verified
Terminal · private key · setup request pasted once
Sign in, create your workspace, and connect Threads.
Open Your assistant, choose Claude Code, and select Create Claude Code setup. Paste the one-time request into Claude Code.
Reload Claude Code and run the first check below.
A synthetic-account read check exists from an earlier adapter build (milestone 3, 2026-08-29). Production onboarding, drafting and image upload through Claude Code have not been verified.
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.
Claude is not one setup surface
Evidence for Claude Desktop does not cover Claude Code, and the reverse. Claude on the web uses the same custom connector path as the desktop app, but it has not been separately checked with Readyweek.