LinkedIn posts with Codex and Bolta
Turn what you ship into social drafts from Codex, with your yes before anything posts. Parts of the Codex route are not confirmed yet, and the note below says which. Nothing goes live on LinkedIn until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
One command or two lines in ~/.codex/config.toml, then codex mcp login bolta opens a Bolta sign-in page. You tick which brands Codex may reach.
Read the top entry in CHANGELOG.md and save a LinkedIn draft about it. Do not schedule it
Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.
What is and is not confirmed
Read this before you set up Codex
- Confirmed: Codex's official docs describe adding a remote MCP server by URL, with a browser sign-in through codex mcp login. Bolta's connection uses exactly that standard route.
- Confirmed: Codex finds skills in folders that contain a SKILL.md file, so the optional Bolta skill is a normal skill for it.
- Not confirmed: nobody at Bolta has run a full draft, review and schedule cycle through Codex yet. Treat the first run as a test and check each result.
- Not confirmed: Bolta's skills README lists npx skills add for Codex CLI, marked not tested. We have not run that install for Codex ourselves.
- Not confirmed: a Bearer API key through bearer_token_env_var, and any Codex-specific plugin entry for Bolta. Sign-in is the path to use.
What Bolta does on LinkedIn
Bolta writes the text, saves it as a draft on the account you name, and waits. Bolta lists each LinkedIn organization as its own account, so a company page is a separate choice from your personal profile.
- Text posts to a personal profile or to a company page you have connected.
- Posts visible to everyone by default, or to connections only if you ask for that.
LinkedIn limits and format rules
Network rules last checked 2026-07-28. Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.
Not promised for LinkedIn from Codex: LinkedIn articles, newsletters and document carousels. LinkedIn supports them, but this page does not confirm that Bolta publishes them. Comment length limits. The one checked limit on this page is the feed post.
| What to know | LinkedIn's own rule | What Bolta does |
|---|---|---|
| Post length | A feed post is capped at 3,000 characters, counting spaces, line breaks, emoji and the full text of any link you paste. | Bolta does not check LinkedIn text length, so LinkedIn may refuse longer text. The draft has to fit before you say yes. |
| Opening lines | The feed cuts a post after the first few lines behind a see more link. | Bolta keeps your first lines as written. Put the point there. |
| Formatting | Not stated on this page. | Plain text only. Bold, italic and headings become look-alike characters, a list becomes bullets, and a link is written as label (url). #hashtags and @mentions are kept as typed. |
| Who can see it | Not stated on this page. | Everyone, unless you set the post to connections only. |
Codex jobs for LinkedIn, and how to write them
- Read the last week of git log and draft a build-in-public thread for review
- Keep one Codex session coding while a second one drafts the launch posts in parallel
- Write to 3,000 characters including spaces, line breaks, emoji and any pasted link, because Bolta will not stop a post that is too long.
Example prompts for LinkedIn
Things to type in Codex. Each one asks for a draft and shows you the text first.
Read the top entry in CHANGELOG.md and save a LinkedIn draft about it. Do not schedule it
Read the top entry in CHANGELOG.md and save a LinkedIn draft about it. Do not schedule it.
Read the top entry in CHANGELOG.md and save a LinkedIn draft about it for my review
Look at the last five commits and draft a LinkedIn post about what changed, without markdown
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Codex asks Bolta for the LinkedIn post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On LinkedIn the exact text includes where the line breaks fall, because the feed hides everything after the first few lines, and how any formatting was flattened to plain text.
- 03
You say yes
Only then does Bolta schedule or publish (publish-post), in your workspace's timezone. Safe Mode, client sign-off and brand approval rules still apply.
Using Codex for LinkedIn
Parts of this route are not confirmed. The note above says which.
For LinkedIn, Codex, from OpenAI, reaches Bolta through codex mcp add, or a [mcp_servers.bolta] entry in config.toml. Sign-in: Sign in (OAuth). The LinkedIn account itself is connected inside Bolta, not in Codex.
Codex is OpenAI's coding agent for the terminal, IDE and desktop app, separate from the ChatGPT chat app. A LinkedIn draft usually starts from what you just shipped, read from files in your project.
An illustration from the Codex guide, not real output. You ask: Read the top entry in CHANGELOG.md and save a LinkedIn draft about it. Do not schedule it. The reply goes along these lines: I read the v2.0 entry, checked your posting rules and saved one LinkedIn draft in your voice. It leads with the faster import and links the release notes. Tell me if you want it shorter, or say yes and I will ask for a time. Draft saved. Waits for your yes.
An illustration from the Codex guide, not real output. You ask: Which of my recent posts got the most reactions? Suggest one follow-up and save it as a draft. The reply goes along these lines: I pulled the analytics for your connected LinkedIn account. The two posts with a screenshot of the product drew the most reactions. I can draft two more in that style and save them for your review. Read only. Offers a draft, saves nothing yet.
Use it to draft or to send work to team review only. Bolta's house rule for unattended runs is no auto-publishing.
Sign in once with codex mcp login bolta on the machine that runs the job. Use --no-browser on a server.
Codex's docs say exec runs in a read-only sandbox by default and expects a Git repository, and that project-defined MCP servers load only for trusted projects. Keep Bolta in your user ~/.codex/config.toml and read the non-interactive page before you wire it into CI.
- Posts from what you shipped. Point Codex at CHANGELOG.md, release notes or a commit range and it saves drafts in your voice. It writes about the change a customer sees.
- Weekly routines. Describe a routine in plain words, for example two build-in-public posts every Friday. Codex shows the plan, and it is saved switched off until you give a separate yes.
- Check the rules for the network. It reads the posting rules for the account, such as length, so the draft fits before you see it.
- Save the draft. The text is saved in Bolta as a draft. It has no time and has not gone anywhere.
- Setup: Try a first draft. Ask: Write three LinkedIn drafts from CHANGELOG.md and save them as drafts. Do not schedule anything. Then approve the exact text in Bolta or in chat. If a Codex command is not found, check Codex's own MCP docs, since command names can change between versions.
- Setup: Add Bolta to Codex. Run codex mcp add bolta --url https://mcp.bolta.ai/mcp. Or open ~/.codex/config.toml, keep what is already there, and add [mcp_servers.bolta] on one line and url = "https://mcp.bolta.ai/mcp" on the next, then save.
- Skill via npx skills add. Run npx skills add boltaai/bolta-skills --skill bolta and choose Codex. Codex finds skills in .agents/skills. We have not run that install for Codex ourselves.
- Codex itself does nothing until you start a session or run codex exec yourself.
- Add Bolta and sign in. Run codex mcp add bolta --url https://mcp.bolta.ai/mcp, then codex mcp login bolta. Sign in on the Bolta page and tick the brands Codex may use.
Connect Codex to Bolta
One command or two lines in ~/.codex/config.toml, then codex mcp login bolta opens a Bolta sign-in page. You tick which brands Codex may reach.
LinkedIn questions, answered for Codex
- How long can a LinkedIn post be when it comes from Codex?
- A LinkedIn feed post is capped at 3,000 characters, and the count includes spaces, line breaks, emoji and the full text of any link you paste. Bolta does not check LinkedIn length, so Codex should write inside the limit and show you the final text before you say yes.
- Can Codex post to a LinkedIn company page and not only my profile?
- Bolta lists each LinkedIn organization as its own account, so you can name the page when you ask (list-accounts). The company page has to be connected in Bolta first. If it is not there, ask for a connect link (get-connect-link) and finish the sign-in in your browser.
- Do I need an API key to connect Codex to Bolta?
- No. The recommended route is a browser sign-in: run codex mcp login bolta and tick the brands to share. Codex can also read a token from an environment variable, but we have not tested that against Bolta, so use sign-in.
- Why did Codex say it cannot schedule my post?
- Usually because nobody has said yes to the exact text yet, or your role in Bolta does not allow it. Bolta refuses on purpose in those cases. Approve the draft, or ask an owner or admin if it is a role limit.
- Codex cannot see my new brand
- A connection only reaches the brands you ticked at sign-in. Run codex mcp login bolta again and tick the new one.
- Codex does not use the Bolta skill
- Start a new codex session after installing it. Check the skill folder is in .agents/skills (in a repo) or ~/.agents/skills, and call it with $ or pick it from /skills.
- Does Codex publish LinkedIn posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that LinkedIn post. Whether Codex completes the connection is not fully confirmed, so read the note above first.
More from Codex
Codex can work with the other networks Bolta publishes to. Each page has its own limits and review notes.
LinkedIn from other AI agents
The same LinkedIn limits apply whichever agent asks. The connection and the setup are what change.
Try a LinkedIn draft from Codex
Connect Codex, ask for a LinkedIn draft and read the exact text. Nothing goes live until you say yes.