Post to Threads from Claude Cowork
Claude Cowork can post to Threads on Threads through ClipSpeed. Add the ClipSpeed connector, sign in, and then ask Claude Cowork to post to Threads, pick the time, and apply Threads's settings, without leaving Claude Desktop's Cowork mode. Threads is coming next on ClipSpeed's rail; this page describes how it works and says so.
Keep a human in the loop: Claude Cowork shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.
Also try
How to post Threads from Claude Cowork
Cowork uses the connectors on your Claude account. Add ClipSpeed once as a custom connector and enable it for the Cowork session. Connect Threads in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup: Claude Desktop → Settings → Connectors
https://api.clipspeed.ai/mcp
# Then ask Claude Cowork:
> Post a one-line take on the launch to Threads at 9am
Claude Cowork: Preview — nothing booked yet. Threads — text under 500. Book it?ClipSpeed has not yet run an end-to-end check inside Cowork specifically. The connector is standard MCP over HTTP with OAuth, which is what Cowork expects; this page is marked accordingly.
- In Claude Desktop, open Settings → Connectors → Add custom connector and paste https://api.clipspeed.ai/mcp.
- Connect and approve the ClipSpeed sign-in.
- Start a Cowork session, give it access to the folder with your recordings or drafts, and enable the ClipSpeed connector.
- Connect Threads in the ClipSpeed app, or ask Claude Cowork for a connect link: it is private, valid for ten minutes, and Threads signs you in itself.
Developer reference: the Claude Cowork MCP page.
What can Claude Cowork do on Threads?
On Threads, Claude Cowork can post 500-character text, images and video to Threads. Every booking runs through the same rules as the ClipSpeed app.
Text, Image and Video posts
Threads takes text, image and video through ClipSpeed. Video: MP4 or MOV up to 1 GB; up to five minutes on Threads. Image: JPG or PNG up to 25 MB.
500 characters, checked at booking
Threads's own arithmetic. Too long is refused with the real count, never trimmed at send time.
Exact time or refused
Name the minute and Claude Cowork books it, or you are told why not and offered the next open slot. A booked Threads post is never moved behind your back.
Preview before anything posts
preview: true runs the whole booking and writes nothing. Claude Cowork shows the plan, with each slot and the day's remaining cap, and books only on your yes.
Clips cut in the same chat
Submit a video or stream link, get captioned 9:16 clips with a viral score, and post the best as native video on Threads. No download, no re-upload.
Pacing and numbers
Planned: Text and image posts on Threads are at least 30 minutes apart, up to 10 a day. Video on Threads is at least 4 hours apart, up to 4 a day under your plan. After a post goes out, Claude Cowork can read back views and engagement where Threads provides them.
How does Claude Cowork post to Threads through ClipSpeed?
You describe what you want in plain language and Claude Cowork makes the ClipSpeed calls. A typical conversation has three beats.
Find your Threads channel
Ask Claude Cowork whether Threads is connected. It calls list_channels and reads platform_settings, so it also knows what Threads accepts and the limits before you write a word.
Compose within the rules
Describe the post. Claude Cowork drafts within Threads's limits; mention a clip or a file and it attaches it.
Schedule or publish
Name a time, or say now. The slot is booked exactly or refused with the next open one, and the reply carries the id you can cancel or edit by.
Threads settings reference
These are the schedule_post fields that apply to Threads. Mention any of them in plain language and Claude Cowork sets them; the server checks them at booking. Fields marked planned land with the Threads release.
| Field | Type | Required | What it does on Threads |
|---|---|---|---|
platforms | string[] | Yes | Include "threads". Up to ten platforms per call; each books its own slot. |
text | string | Yes for a text post | Up to 500 characters. One link per post is clickable. |
hashtags | string[] | No | Threads treats the first tag as its topic tag; keep it to one. |
media_kind | text | image | video | No | Detected from the file when omitted. |
clip_id or media_url | string | No | A ClipSpeed clip or a public link to an image or a video up to five minutes. |
scheduled_at | ISO 8601 | No | Exact or refused with the next open slot. |
preview | boolean | No | Plan only. |
Common Threads configurations
Ask Claude Cowork for any of these and it applies the matching settings.
Short text post
Clip as video
Image with a topic tag
Ten posts, previewed
Example prompts for Threads in Claude Cowork
Type these into Claude Desktop's Cowork mode. Claude Cowork calls ClipSpeed and confirms before publishing.
Post Threads with a scheduled time
Post a one-line take on the launch to Threads at 9am. Keep the text under 500 characters. Preview first.
Cut the clips, then post the best
Clip this link, keep the top three by viral score, and schedule them to Threads at 11am, 3pm and 7pm tomorrow. Show me the plan before booking.
Check and adjust the Threads calendar
What is scheduled on Threads this week? Cancel tomorrow's post and tell me the next open Threads slot on Friday.
Threads limits and gotchas to know
Threads enforces a few rules that Claude Cowork and ClipSpeed respect automatically, but knowing them helps you phrase requests.
- 500 characters per post. Longer is refused at booking with the real count.
- Threads uses a single topic tag per post rather than a list of hashtags. Ask for one.
- Replies and multi-post threads are not part of the first release. One post per booking.
- Threads is the next rail. Until it posts, bookings to Threads are refused with a plain message and the badge says Coming soon.
- Planned pacing: ten text or image posts a day 30 minutes apart, video four hours apart.
| Rule | Threads |
|---|---|
| Accepts | Text, Image, Video |
| Text limit | 500 characters |
| Title | No title field |
| Links in the caption | Kept; one link per post is clickable |
| Pacing | Planned: Text and image posts on Threads are at least 30 minutes apart, up to 10 a day. Video on Threads is at least 4 hours apart, up to 4 a day under your plan. |
| Formats | Image: JPG or PNG up to 25 MB. Video: MP4 or MOV up to 1 GB; up to five minutes on Threads. Aspect: any; 9:16 or 1:1 |
| Status | Coming next on ClipSpeed's rail; bookings are refused with a plain message until then |
What Postiz-style schedulers cannot do
Cut the clips first
Claude Cowork does not need finished video to start. Hand it a YouTube link, a podcast, a stream VOD or a local export. ClipSpeed finds the moments, cuts them to 9:16 with word-by-word captions, scores each one 0 to 100 for shareability, and returns them in the same conversation. Claude Cowork picks by score, writes the caption from the transcript, and books the clips on Threads. Three tool calls, one approval, no download and no re-upload.
- Clips arrive with a title written from the hook, a transcript and a viral score, so the agent can choose and caption without watching the footage.
- Live streams can be clipped while they are still on air; the agent books the highlights for the next morning before the stream ends.
- Every clip is already hosted, so
schedule_posttakes its id directly. Nothing moves through your laptop.
submit_to_clipspeedPaste the link. ClipSpeed starts the job and returns a project id.check_clipsPoll with the project id. Back come the finished 9:16 clips with titles, transcripts, viral scores and preview links.schedule_postPass the clip id, the platforms, a caption and a time. Claude Cowork shows the plan with preview: true, you say yes, it books.generate_image or generate_videoDescribe the shot. ClipSpeed runs it on the model that fits (Seedance, Kling, Veo, Nano Banana Pro, GPT Image and others) and quotes the credits first.wait_for_generationReturns the hosted result link and a preview the agent can show you.schedule_post with media_urlThe result link goes straight into the booking on Threads. The caption, the time and the file are approved together.The other half nobody else has
Generate the image or video, then post it
A product shot for Instagram, a 16:9 announcement graphic for X, a six-second opener before a clip: Claude Cowork can make an image or a short video with ClipSpeed's image and video models and book the result in the same reply. There is no separate design tool, no export, no upload page. The generated file is hosted, so media_url is the only thing the booking needs.
- The price in credits is quoted before anything renders, within the per-generation and daily caps you set in Settings.
- Results are previewed in the conversation, so you approve the picture and the post at once.
- Images post as JPG, PNG or WebP up to 25 MB; video posts as MP4, MOV or WebM up to 1 GB.
What is Claude Cowork?
Claude Cowork is the agent mode in Claude Desktop for knowledge work: it operates on folders, files and desktop apps with less supervision than a chat, and uses the same connectors as claude.ai. With the ClipSpeed connector enabled, Cowork can take a folder of recordings, clip them, write the posts and book them.
How ClipSpeed works with Claude Cowork
- Cowork uses the account's connectors; ClipSpeed's tools are available when enabled
- It reads platform rules before composing
- Exact-or-refused booking with the next open slot named
preview: truefor the plan before booking- OAuth sign-in, no passwords in the session
Claude Cowork vs Claude Code vs Claude: Claude Cowork (claude desktop), Claude Code (terminal), Claude (chat). This page is about Claude Cowork; the Claude Cowork guide compares them.
Connector type: Custom (MCP)
Name: ClipSpeed
URL: https://api.clipspeed.ai/mcp
Auth: OAuth
# Enable the connector in the Cowork session and grant the folder.# What the agent reads at connect time (tool descriptions, abridged)
list_channels Connected platforms, what each accepts, limits, your time zone
connect_channel A private 10-minute link to connect one platform
platform_settings Limits, title rules, link handling, pacing per platform
schedule_post clip_id | text | media_url → platforms[], scheduled_at, preview
list_scheduled_posts Scheduled, sending, posted, failed — with post links
update_scheduled_post Edit copy while still scheduled (the time never moves)
cancel_scheduled_post Cancel; undoable 72 h in the app
post_analytics Views, likes, comments, shares where the platform gives them
submit_to_clipspeed Start clipping a video or stream link → projectId
check_clips Finished 9:16 clips with titles, transcripts, viral scores
generate_image / generate_video / wait_for_generation
# Threads: text/image/video · text 500Post to Threads and other platforms from Claude Cowork
One request can book the same content to Threads and other channels, each keeping its own settings and its own slot. Every platform below has its own Claude Cowork guide.
Also works with
Threads and Claude Cowork: frequently asked questions
How do I post to Threads from Claude Cowork?
In Claude Desktop, open Settings → Connectors → Add custom connector and paste https://api.clipspeed.ai/mcp. Connect and approve the ClipSpeed sign-in. Connect Threads in ClipSpeed (or ask Claude Cowork for a connect link; it is private and valid for ten minutes), then describe the post in plain language. Claude Cowork reads the Threads rules, drafts within them, shows the plan and books on your yes. Threads is coming next; until the badge changes, the booking is refused with a plain message.
What can Claude Cowork post to Threads through ClipSpeed?
Post 500-character text, images and video to Threads. Threads takes text, image and video posts. Text is limited to 500 characters.
Which Threads settings can Claude Cowork control?
The fields in the settings reference above: text, hashtags, media_kind, clip_id or media_url, scheduled_at, preview. Mention any of them in plain language ("unlisted", "tomorrow at 9", "preview first") and Claude Cowork sets the matching field before it books.
Do I need a Threads API key or developer account?
No. You connect Threads to ClipSpeed once through Threads's own sign-in, and Claude Cowork talks to ClipSpeed over OAuth. No Threads developer key, bearer token or password is pasted anywhere.
How many Threads posts a day can Claude Cowork schedule?
Planned: Text and image posts on Threads are at least 30 minutes apart, up to 10 a day. Video on Threads is at least 4 hours apart, up to 4 a day under your plan. When a time is taken, the booking is refused with the next open slot rather than moved. Ask for preview to see a day's plan and the remaining cap before anything is booked.
Can posts go out to Threads while I am away?
Yes. Once booked, ClipSpeed publishes at the scheduled minute whether or not Claude Cowork is open. For unattended runs that decide what to post, use a headless agent such as Claude Code or Codex with the same account.
Is posting to Threads from Claude Cowork different from Claude Code?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. Claude Cowork: claude desktop (mac and windows). Claude Code: terminal, repo, headless, ci.