Post to LinkedIn from Codex
Codex can post text, images and video on LinkedIn through ClipSpeed. Add the ClipSpeed server with one command, sign in, and then ask Codex to post text, images and video, pick the time, and apply LinkedIn's settings, without leaving the terminal and IDE.
Keep a human in the loop: Codex shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.
Also try
How to post LinkedIn from Codex
One command writes the server into Codex's config. Start codex, sign in to ClipSpeed when it asks, and the tools are available. Connect LinkedIn in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup (OAuth, no API key)
codex mcp add clipspeed --url https://api.clipspeed.ai/mcp
# Then ask Codex:
> Read CHANGELOG.md and write a LinkedIn post about v2.4 under 1,200 characters, post Tuesday 8:30am
Codex: Preview — nothing booked yet. LinkedIn — text only. Book it?Codex stores MCP servers in ~/.codex/config.toml under [mcp_servers.clipspeed]. You can also paste the block by hand.
- Run codex mcp add clipspeed --url https://api.clipspeed.ai/mcp in your terminal.
- Start codex. On first use of a ClipSpeed tool it opens the OAuth sign-in; approve it.
- Ask it to list your channels to confirm.
- Connect LinkedIn in the ClipSpeed app, or ask Codex for a connect link: it is private, valid for ten minutes, and LinkedIn signs you in itself.
Developer reference: the Codex MCP page.
What can Codex do on LinkedIn?
On LinkedIn, Codex can post long-form text, images and native video to your profile. Every booking runs through the same rules as the ClipSpeed app.
Text, Image and Video posts
LinkedIn takes text, image and video through ClipSpeed. Text-only posts work today. Video: MP4, MOV or WebM up to 1 GB by public link, or a finished ClipSpeed clip. Image: JPG, PNG, WebP or GIF up to 25 MB by public link.
3,000 characters, checked at booking
LinkedIn's own arithmetic. Too long is refused with the real count, never trimmed at send time.
Exact time or refused
Name the minute and Codex books it, or you are told why not and offered the next open slot. A booked LinkedIn post is never moved behind your back.
Preview before anything posts
preview: true runs the whole booking and writes nothing. Codex shows the plan, with each slot and the day's remaining cap, and books only on your yes.
Clips cut in the same session
Submit a video or stream link, get captioned 9:16 clips with a viral score, and post the best as native video on LinkedIn. No download, no re-upload.
Pacing and numbers
Text and image posts on LinkedIn are at least 60 minutes apart, up to 3 a day. Video on LinkedIn is at least 4 hours apart, up to 2 a day under your plan. After a post goes out, Codex can read back views and engagement where LinkedIn provides them.
How does Codex post to LinkedIn through ClipSpeed?
You describe what you want in plain language and Codex makes the ClipSpeed calls. A typical conversation has three beats.
Find your LinkedIn channel
Ask Codex whether LinkedIn is connected. It calls list_channels and reads platform_settings, so it also knows what LinkedIn accepts and the limits before you write a word.
Compose within the rules
Describe the post. Codex drafts within LinkedIn'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.
LinkedIn settings reference
These are the schedule_post fields that apply to LinkedIn. Mention any of them in plain language and Codex sets them; the server checks them at booking.
| Field | Type | Required | What it does on LinkedIn |
|---|---|---|---|
platforms | string[] | Yes | Include "linkedin". Up to ten platforms per call; each books its own slot. |
text | string | Yes for a text post | Up to 3,000 characters. The first 210 or so show before 'see more', so the agent is told to put the point first. |
hashtags | string[] | No | Appended and counted toward 3,000. Three to five is the norm. |
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 https link to an image up to 25 MB or a video up to 1 GB. Leave both out for a text post. |
scheduled_at | ISO 8601 | No | Exact or refused with the next open slot. Omit to post as soon as possible. |
preview | boolean | No | Plan only; nothing is booked. |
Common LinkedIn configurations
Ask Codex for any of these and it applies the matching settings.
Text post from a changelog
Native video from a clip
Image post with a generated graphic
Three a week, previewed
Example prompts for LinkedIn in Codex
Type these into the terminal and IDE, or pass one to nightly.sh in a script. Codex calls ClipSpeed and confirms before publishing.
Post LinkedIn with a scheduled time
Read CHANGELOG.md and write a LinkedIn post about v2.4 under 1,200 characters, post Tuesday 8:30am. Keep the text under 3,000 characters. Preview first.
Cut the clips, then post the best
Clip this link, keep the top three by viral score, and schedule them to LinkedIn at 11am, 3pm and 7pm tomorrow. Show me the plan before booking.
From a script with Codex
codex exec "Summarise the changes since the last git tag as one LinkedIn post under 3,000 characters. Schedule it via ClipSpeed for today at 10am; preview first and book if nothing is refused."
LinkedIn limits and gotchas to know
LinkedIn enforces a few rules that Codex and ClipSpeed respect automatically, but knowing them helps you phrase requests.
- 3,000 characters including hashtags. Over that, the booking is refused with the exact count, never trimmed.
- LinkedIn shows roughly the first 210 characters before 'see more'. Tell the agent to lead with the point.
- Video on LinkedIn is capped at two posts a day, four hours apart, because more than that reads as spam and hurts your own reach. Text and image posts are capped at three a day, an hour apart.
- Company pages are not part of the agent tools today. Posts go to the profile you connected; this page does not claim pages until they post.
- Carousels and documents are not supported. One image, one video or text only per post.
| Rule | |
|---|---|
| Accepts | Text, Image, Video (text-only posts work today) |
| Text limit | 3,000 characters |
| Title | No title field |
| Links in the caption | Kept; LinkedIn turns the first link into a preview card |
| Pacing | Text and image posts on LinkedIn are at least 60 minutes apart, up to 3 a day. Video on LinkedIn is at least 4 hours apart, up to 2 a day under your plan. |
| Formats | Image: JPG, PNG, WebP or GIF up to 25 MB by public link. Video: MP4, MOV or WebM up to 1 GB by public link, or a finished ClipSpeed clip. Aspect: 1:1 or 4:5 for images, 9:16 or 1:1 for video |
| Status | Posting today |
What Postiz-style schedulers cannot do
Cut the clips first
Codex 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. Codex picks by score, writes the caption from the transcript, and books the clips on LinkedIn. 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. Codex 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 LinkedIn. 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: Codex 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 Codex?
Codex is OpenAI's coding agent. It runs in the terminal (codex), inside IDEs, and in the cloud, reads your codebase, runs commands and calls MCP tools. With ClipSpeed added as an MCP server, Codex can clip a video, generate images and video, and schedule posts, interactively or from a script with codex exec.
How ClipSpeed works with Codex
- codex mcp add writes the server into config.toml; Codex discovers the tools at start
- It reads
platform_settingsbefore writing so limits are met schedule_postis exact or refused with the next open slot; nothing moved quietlypreview: truereturns the plan with nothing bookedcodex exectakes one prompt and exits, for cron and CI
Codex vs ChatGPT: Codex (terminal, ide, cloud), ChatGPT (chatgpt.com). This page is about Codex; the Codex guide compares them.
# Written by: codex mcp add clipspeed --url https://api.clipspeed.ai/mcp
[mcp_servers.clipspeed]
url = "https://api.clipspeed.ai/mcp"
# For a runner with no browser, authenticate with an API key instead:
# bearer_token_env_var = "CLIPSPEED_API_KEY"
# Verify
$ codex "List my connected ClipSpeed channels"# 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
# LinkedIn: text/image/video · text 3,000Post to LinkedIn and other platforms from Codex
One request can book the same content to LinkedIn and other channels, each keeping its own settings and its own slot. Every platform below has its own Codex guide.
Also works with
LinkedIn and Codex: frequently asked questions
How do I post to LinkedIn from Codex?
Run codex mcp add clipspeed --url https://api.clipspeed.ai/mcp in your terminal. Start codex. On first use of a ClipSpeed tool it opens the OAuth sign-in; approve it. Connect LinkedIn in ClipSpeed (or ask Codex for a connect link; it is private and valid for ten minutes), then describe the post in plain language. Codex reads the LinkedIn rules, drafts within them, shows the plan and books on your yes.
What can Codex post to LinkedIn through ClipSpeed?
Post long-form text, images and native video to your profile. LinkedIn takes text, image and video posts, and text-only posts work today. Text is limited to 3,000 characters.
Which LinkedIn settings can Codex 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 Codex sets the matching field before it books.
Do I need a LinkedIn API key or developer account?
No. You connect LinkedIn to ClipSpeed once through LinkedIn's own sign-in, and Codex talks to ClipSpeed over OAuth. No LinkedIn developer key, bearer token or password is pasted anywhere.
How many LinkedIn posts a day can Codex schedule?
Text and image posts on LinkedIn are at least 60 minutes apart, up to 3 a day. Video on LinkedIn is at least 4 hours apart, up to 2 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 Codex post to LinkedIn from a script or a cron job?
Yes. Codex's headless mode (nightly.sh) runs one prompt and exits, and the ClipSpeed server registered on that machine does the booking. On a runner with no browser, authenticate with a ClipSpeed API key header. Keep preview on so the run reports a plan before it books.
Is posting to LinkedIn from Codex different from ChatGPT?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. Codex: terminal, vs code and other ides, codex cloud. ChatGPT: chatgpt.com, conversation first; confirms each write.