Schedule social media posts with Codex
Codex is OpenAI's coding agent for the terminal, the IDE and the desktop app. Add Bolta to it as a hosted MCP server and it can turn a changelog or git log into posts in your brand voice, list what is waiting for review, and read analytics. Nothing is scheduled or published until you approve the exact text.
- Paste a changelog or git log, get launch posts saved as drafts in your voice
- Add Bolta with one command, then sign in in the browser: no API key to copy
- Codex drafts and you decide: nothing posts until you say yes to the exact text
Nothing is approved, scheduled or published 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.
Two steps to a first draft
- 01
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.
- 02
Start a new session and ask
Open a fresh codex session and type: What is waiting for my yes in Bolta? Then ask for a first draft from CHANGELOG.md. Approve the text before anything goes out.
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.
How Codex uses Bolta
Codex calls Bolta's tools over MCP. The steps below are what happens for a post about something you just shipped. None of them publishes.
- 01
Find the right brand
Codex asks Bolta which organizations and brands this connection may reach, so a post about your side project does not land on the company brand.
list-workspaces - 02
See which accounts are connected
It lists the social accounts on that brand, so it knows whether LinkedIn, X or Bluesky is an option.
list-accounts - 03
Learn how you write
Before drafting from your changelog, it reads your voice and brand context, so the draft sounds like you and not like release notes.
get-voice-context - 04
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.
get-posting-rules - 05
Save the draft
The text is saved in Bolta as a draft. It has no time and has not gone anywhere.
save-post - 06
Wait for your yes
Codex shows you the exact text. Only after you approve it does anything get a time or go out. This step is you, not a tool.
Set up Codex
Connect once. Everything below works from Codex afterwards.
- 01
Check what you need
You need a Bolta account with at least one brand, and Codex installed. Run codex in a terminal to confirm it starts. Codex's MCP docs say the CLI, the IDE extension and the desktop app share this configuration, so the same entry should apply if you use those instead.
- 02
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.
- 03
Sign in to Bolta
Run codex mcp login bolta. A Bolta page opens in your browser. Sign in and tick the brands this connection may reach. One connection is one organization, and it can only reach the brands you tick.
- 04
On a machine with no browser
Run codex mcp login bolta --no-browser. Codex prints a link. Open it on any computer, sign in, then paste the full address you land on back into the terminal.
- 05
Check that Codex sees Bolta
Run codex mcp list and look for bolta. Or start codex and type /mcp to see the active servers.
- 06
Add the Bolta skill
Optional, and it helps Codex follow your voice, your review list and the approval rule. Run npx skills add boltaai/bolta-skills --skill bolta and choose Codex if it asks. Codex looks for skills in .agents/skills inside a repo or ~/.agents/skills for your user.
- 07
Start a new session
Close any open Codex session and start a new codex one so it picks up the server and the skill.
- 08
Test with a read-only question
Ask: What is waiting for my yes in Bolta? Allow the tool call if Codex asks. This reads your review list and changes nothing.
- 09
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.
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.
Which Bolta connection methods work with Codex
Sign-in is the route to use. Nothing here has been run end to end through Codex, so only the script route, which does not involve Codex, is marked as working.
| Method | With Codex | How |
|---|---|---|
| Hosted MCP with sign-in | Not confirmed | Run codex mcp add bolta --url https://mcp.bolta.ai/mcp, then codex mcp login bolta. This is the route in Codex's own docs for a remote server with sign-in, and the one we recommend. We have not run a full draft-to-schedule cycle through it. |
| MCP with an API key | Not confirmed | Codex can read a token from an environment variable named in bearer_token_env_var, and Bolta accepts Bearer keys. We have not tested that pairing, so use sign-in. |
| Skill via npx skills add | Not confirmed | 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. |
| Plugin or extension | Not confirmed | Codex has plugins that bundle skills and connectors, but nobody here has checked a Bolta entry for it. Do not rely on one. |
| REST API from a script | Works | A script you write can call Bolta's REST API with an Authorization: Bearer key from your Bolta settings, with no Codex involved. See the API docs. This is separate from the MCP connection. |
What you can run in Bolta from Codex
Each row is an area of Bolta, with the real tools behind it.
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.
get-voice-contextget-posting-rulessave-postReview and approval
Ask what is waiting for your yes, read each draft back, then approve or reject with your own reason. Bolta wants the exact text before a post is approved.
list-inbox-itemsapprove-many-postsreject-postWeekly 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.
planconfirm-planactivate-routineVoice and brand
Codex can read your brand context and voice so drafts match how you write, and it can help set up a voice profile from samples.
get-voice-profilecreate-voice-profilelist-business-dnaResults
Ask which of your recent posts did best, then ask for a follow-up draft in the same style. Reading results changes nothing.
list-accountsget-account-analyticsReplies
It can draft a reply to a comment and show it to you first. Sending a reply needs your yes like any other post.
list-engagementsdraft-engagement-replyTeams and clients
If you work with a team, Codex can send drafts to review instead of keeping them to itself. What it can do still depends on your role in Bolta.
list-workspace-memberssubmit-for-review
A sample session in Codex
A made-up exchange to show the order of events. It is not real output.
- You
What is waiting for my yes in Bolta?
- Tool call
list-inbox-itemsReads the review list. Changes nothing.
- Codex
Nothing is waiting. Want me to draft something from CHANGELOG.md?
- You
Yes. Read the top entry and write a LinkedIn post about it. Save it as a draft.
- Tool call
list-workspacesChecks which brand this connection reaches.
- Tool call
get-voice-contextReads how this brand writes.
- Tool call
get-posting-rulesChecks LinkedIn limits.
- Tool call
save-postSaves the text as a draft with no time.
- Codex
I saved a draft that leads with the faster import and links the release notes. It is not scheduled. Here is the exact text. Want it shorter, or do you approve it?
- You
Cut the last line and keep it as a draft for now.
- Tool call
save-postSaves the shorter text. Still a draft with no time.
- Codex
Done. I removed the last line and kept it as a draft. It stays unscheduled until you say yes to the final text and give me a time.
Command or config file?
Both write the same MCP entry. Pick the one that fits how you set up Codex.
codex mcp add
Choose this if you want it done in one line.
Run codex mcp add bolta --url https://mcp.bolta.ai/mcp, then codex mcp login bolta. Nothing to edit by hand.
config.toml
Choose this if you keep your Codex settings in version control.
Add [mcp_servers.bolta] and url = "https://mcp.bolta.ai/mcp" to ~/.codex/config.toml, or to .codex/config.toml in a trusted project. Then run codex mcp login bolta.
What can Codex do with Bolta?
- Turn a release note or CHANGELOG.md entry into a LinkedIn and an X draft the day you ship
- 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
- Have a script call codex exec to save a weekly draft batch for your team to review
- Check which recent posts did best before Codex suggests what to write next
- Set up a weekly routine from the terminal that drafts posts and waits for your approval
What is the Bolta MCP?
The server Codex talks to when it works with Bolta.
MCP, the Model Context Protocol, is the open standard that lets an AI app call tools in another product. Bolta runs a hosted MCP server at https://mcp.bolta.ai/mcp. Your AI app discovers its 67 tools and calls them for you: list your brands, save a draft, plan a routine, read results.
One connection is one organization. You tick the brands the app may reach, and every call is checked against your role, so the app can never do more in Bolta than you can. Approving, scheduling and publishing need your yes.
Brands & accounts6 tools
The brands this connection reaches, who works on them and who can approve, their approval settings, connected social accounts, and each platform's posting rules.
list-workspaces, list-workspace-members, set-brand-approval, list-accounts, get-connect-link, get-posting-rules
Posts9 tools
Save a draft or edit a post with save-post, then publish it now or at a time with publish-post after the user says yes.
list-workspace-posts, get-post, save-post, publish-post, delete-post, bulk-create-posts, create-wordpress-blog-post, list-recently-deleted, restore-deleted
Review4 tools
Everything waiting for a yes: submit drafts to the team or send them to a named person for approval, approve one or many, reject with a reason, and work the inbox of routine and campaign drafts.
list-inbox-items, submit-for-review, approve-many-posts, reject-post
Plans6 tools
Have Bolta plan a routine or a campaign the way its own chat does, change it, then save it on the user's yes.
plan, plan-routine, plan-campaign, recommend-routines, revise-plan, confirm-plan
Routines10 tools
Work that repeats and runs in Bolta even with the app closed.
list-routine-templates, list-routines, get-routine, create-routine, update-routine, activate-routine, pause-routine, archive-routine, run-routine-now, list-routine-runs
Campaigns6 tools
One to four weeks of posts about one thing: a launch, an event, a season.
list-content-campaigns, get-content-campaign, create-content-campaign, update-content-campaign, analyze-content-campaign-source, set-content-campaign-status
Team versions4 tools
One idea written as one post per person on the team, each in their own voice.
plan-team-posts, update-team-post-plan, generate-team-post-drafts, get-team-post-plan
Voice & business8 tools
The brand's voice and business facts, and writing in that voice.
get-voice-context, get-voice-profile, create-voice-profile, update-voice-profile, list-business-dna, extract-business-dna, update-business-dna, voice-generate
Suggestions2 tools
What Bolta suggests changing, for a routine or the whole brand, from what people approved, edited and rejected.
list-suggestions, decide-suggestion
Replies10 tools
Find conversations worth joining, draft replies in the brand voice, and send them once the user says yes.
search-engagement-opportunities, list-engagements, get-social-content, draft-engagement-reply, draft-inbound-reply, publish-engagement-reply, reply-to-social-content, react-to-social-content, send-outreach-reply, update-outreach-reply
Results2 tools
How posts and accounts are performing.
list-account-insights, get-account-analytics
Ship it, then post about it
Sample replies show the shape of what Codex does with Bolta. Your real replies will differ.
Read the top entry in CHANGELOG.md and save a LinkedIn draft about it. Do not schedule it.
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.
get-posting-rules, save-post
What is waiting for my yes in Bolta right now?
You have three items to review: two drafts from the weekly routine and one reply suggestion. I have not approved anything. Want me to show the exact text of the first draft?
list-inbox-items
Set up a weekly routine that drafts two build-in-public posts every Friday, and send them to review.
Here is the plan: every Friday it drafts two build-in-public posts and puts them in your review list. It runs in Bolta, so it cannot read your repo. Nothing is saved yet. Say yes and I will save it switched off, then it needs a separate yes before it runs.
plan
Which of my recent posts got the most reactions? Suggest one follow-up and save it as a draft.
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.
list-accounts, get-account-analytics
Look at the last ten commits and write an X thread about what changed. Save it as a draft only.
I grouped the ten commits into three changes a customer would notice, left out the refactors, and saved a four-post thread as a draft. Nothing is scheduled. Tell me what to cut, or say yes to the exact text when you are happy with it.
get-voice-context, save-post
I run two brands. Draft a Bluesky post about the new export button for the side-project brand, not the main one.
You ticked two brands at sign-in, so I used the side-project brand and checked its posting rules before writing. The draft is saved there. The main brand has nothing new.
list-workspaces, get-posting-rules, save-post
Send the three drafts I just wrote to my teammate for review instead of keeping them to myself.
I can send them to review in Bolta so a teammate sees them in their list. I have not approved them. Tell me which teammate and I will confirm before sending.
list-workspace-members, submit-for-review
Where a draft can go
- X
- Threads
- Bluesky
- Mastodon
- TikTok
Only accounts you have connected in Bolta. Codex cannot post anywhere else.
What keeps running when Codex is closed
A Codex session only works while it is open. Anything that should happen later lives in Bolta, not in the terminal.
- A routine saved and switched on in Bolta keeps running when no session is open. It drafts and sends to review.
- A draft already saved in Bolta stays put until you approve it. Closing the terminal does not lose it.
- Scheduled posts you approved earlier still go out at their time, because Bolta holds them.
- Codex itself does nothing until you start a session or run codex exec yourself.
A scheduled codex exec job from your own machine or CI should only save drafts or send to team review. Bolta's rule for unattended runs is no auto-publishing, and we have not tested codex exec with Bolta.
Turn a changelog or git log into drafts
Codex already has your repo open, which makes it a good starting point for launch posts. Point it at the file or the commit range and ask for drafts.
- 01
Name the source
Say which file or range to read, for example CHANGELOG.md, the release notes for v2.0, or the last week of git log.
- 02
Say where it goes
Name the network and the brand if you ticked more than one, for example a LinkedIn post for the Acme brand.
- 03
Ask for a draft, not a post
Add save it as a draft, do not schedule. Codex saves it in Bolta and shows you the text.
- 04
Approve the exact text
Edit it in chat or in Bolta. Only when you say yes does it get a time or go out.
Headless runs with codex exec
Codex has a non-interactive mode, codex exec, for scripts and scheduled jobs. It should be able to call Bolta the way a normal session does once the server is added and signed in on that machine, but we have not run that.
- 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.
The skill, and which brand Codex uses
The MCP connection gives Codex the tools. The skill and your brand choice shape how it uses them.
| Question | Answer |
|---|---|
| Do I need the skill? | No. Codex can use Bolta without it. The skill teaches it your voice, your review list and the approval rule. |
| Where does Codex look for skills? | .agents/skills in a repo, or ~/.agents/skills for your user. You can call one with $ or from /skills. |
| Which brands can it reach? | Only the brands you ticked at sign-in. One connection is one organization. |
| How do I use another brand? | Name the brand in your request. To add one later, run codex mcp login bolta again and tick it. |
One session codes, another drafts
Codex can run more than one session, so the launch post does not have to wait for the feature to finish.
- Keep the coding session on the branch. Open a second codex session in the same repo just for the announcement.
- In the second session, ask it to read the diff or CHANGELOG.md and save drafts. It does not need to touch your code.
- Both sessions use the Bolta connection you already signed in. Each one needs to be started after you added the server.
- If you would rather not mix the two, keep a separate folder that holds only the Bolta skill and your notes on tone.
User config or project config
Codex reads MCP servers from a user file and, in a trusted project, from the project too. Which one you pick decides who gets Bolta.
Codex's docs say project-defined MCP servers load only for trusted projects. The entry on this page holds only the Bolta server address. Each person signs in themselves with codex mcp login bolta.
| File | Who sees it | Good for |
|---|---|---|
| ~/.codex/config.toml | You, in every project | A founder with one Bolta organization who drafts from any repo |
| .codex/config.toml in a trusted project | Anyone who opens that project and trusts it | A team that wants the same brand on a shared repo |
What not to hand Codex to post about
A repo holds more than release notes. Codex can read a lot, so tell it what is safe to talk about.
- Name the file or range to read. Leave out private branches, security fixes not yet shipped and customer names in commit messages.
- Ask for the customer-facing change, not the internal reason. Commit messages are written for developers.
- Read every draft before you say yes. Codex can summarise a commit wrongly, and Bolta checks the post against your brand rules but not against your code.
What is tested and what is not
The connection is the standard Codex route for a remote MCP server, and the commands on this page come from Codex's own documentation. What we have not done is run a complete draft, review and schedule cycle through Codex.
Claude Code is the most tested coding-agent path for Bolta. If you want the proven route today, use that. If you prefer Codex, expect to check each step the first time.
What Codex cannot do without you
Codex connects as: codex mcp add, or a [mcp_servers.bolta] entry in config.toml.
Drafts are free, finals need your yes
Codex can write, edit and save drafts at any time. Approving, scheduling, publishing, sending a reply, activating a routine or campaign and deleting each wait for your yes, shown against the exact text.
One connection, one organization
When you connect Codex you tick the brands it may reach. It reaches only those, and when that is more than one brand, every call names the brand it is for.
Your role is the ceiling
Each call Codex makes is checked like a normal request from you. Owners and admins can act on any post, creators on Bolta's drafts and on posts they are a named reviewer on, and viewers never approve or publish.
Where Codex can publish through Bolta
11 social networks, plus WordPress for articles. Bolta holds the connected accounts. Each card opens the Codex guide for that network.
- Threadstext posts, image posts, polls
- LinkedIntext posts, articles, carousels
- X (Twitter)tweets, threads, polls
- Instagramposts, stories, reels
- Facebookposts, stories, reels
- Blueskyposts, threads, quote posts
- Mastodontoots, polls, threads
- Reddittext posts, link posts, image posts
- TikTokvideos, stories, photo posts
- YouTubevideos, Shorts, community postsTeam plan, beta
- Pinterestpins, idea pins, video pinsTeam plan, beta
The words behind Codex and Bolta
For Codex: codex mcp add, or a [mcp_servers.bolta] entry in config.toml, signing in with Sign in (OAuth).
- MCP
- The Model Context Protocol, an open standard that lets an AI app call tools in another product. Bolta's hosted server is at https://mcp.bolta.ai/mcp, and Codex reaches Bolta through a connection like it.
- Skill
- A folder of instructions an AI app reads so it knows how to use Bolta well. It does not connect by itself: install it with
npx skills add boltaai/bolta-skills --skill boltanext to the connection. - Plugin
- A bundle that brings the connection and the skill in one install, where the app supports plugins. Claude Code has one, added with its plugin marketplace commands.
- API key
- A
bolta_sk_key you create in Settings, sent as a Bearer header. It carries the permissions you choose, which suits apps you configure by hand or anything that runs unattended.
Setup for Codex is only partly confirmed. See what is and is not confirmed. Last checked 2026-11-21.
Codex is not ChatGPT
Codex is OpenAI's coding agent for the terminal, IDE and desktop app, and you add Bolta in its config. ChatGPT is the chat app, and it has its own Bolta setup. Use the page that matches the tool you actually open.
Other AI agents that post through Bolta
Every agent below connects to the same Bolta workspace and follows the same approval rules.
- ChatGPTOpen Bolta in ChatGPT, sign in
- OpenAI dotsAlways-on ChatGPT agents
- ClaudeCustom connector, one sign-in
- Claude DuetCarries your Claude connectors over
- Claude CoworkPlugin and connector on your desktop
- Claude CodeTwo plugin commands
- CursorOne mcp.json entry
- GeminiGemini CLI extension
- OpenClawSkills and MCP for your gateway
- Hermes AgentMCP server in the Hermes config
- Grok BotCustom connector in xAI's agent
- Grok Buildgrok mcp add
- DeepSeekThrough the Bolta MCP link
- Kimi K3Kimi Code with the Bolta MCP server
- MuseMeta's agent, Muse Code and connectors
- ManusConnector with an API key
- CueA personal agent that posts for you
- PerplexityResearch there, draft in Bolta
- Perplexity ComputerRemote MCP connector
- nanoclawRun it from WhatsApp or Telegram
- PaperclipConnector for your agent company
- MCP ServerOne link for any MCP client
Related
What Codex can do through Bolta
The jobs Bolta's agents cover, each with its own page. Your AI app can ask for drafts, plans and reports in the same areas. Every post still waits for your yes.
Frequently asked questions
Short answers about using Codex with Bolta.
- Is Codex the same as ChatGPT, and do I use the same Bolta setup?
- No. Codex is OpenAI's coding agent for the terminal, IDE and desktop app. ChatGPT is the chat app with its own Bolta page. Use the setup on this page for Codex.
- 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.
- Can Codex publish to my social accounts without my approval?
- No. A post only gets a time or goes out after you say yes to its exact text. Codex should show you the text first, and if it tries to skip that, Bolta refuses or keeps the post in review. Your role and Safe Mode still apply.
- How do I connect Codex when I am on a server with no browser?
- Run codex mcp login bolta --no-browser. Codex prints a link, you open it on any computer and sign in, then paste the full address you land on back into the terminal.
- Can I run Bolta from codex exec in a script or CI?
- It should work once the server is added and signed in on that machine, but we have not tested it. Keep unattended runs to saving drafts or sending to team review. Do not set them up to publish on their own.
- Which brands can Codex reach, and how do I add another one?
- Only the brands you ticked at sign-in, since one connection is one organization. With more than one ticked, say which brand a draft is for, for example the side project and not the main one. To add another, run codex mcp login bolta again and tick it.
- Do I need the Bolta skill if the MCP connection already works?
- No, the connection is enough to start. The skill helps Codex use your voice, your review list and the approval rule more consistently. Install it with npx skills add boltaai/bolta-skills --skill bolta and start a new session.
- Does it cost extra to use Codex with Bolta?
- We have not confirmed Codex's pricing or which plans include it, so check OpenAI's pages. Plan limits and credit use for what you draft are shown in Bolta.
- Is this tested end to end?
- Not yet. The connection follows Codex's documented route, but no one has run a full draft, review and schedule cycle through Codex. Claude Code is the most tested path.
- What can Codex not do through Bolta?
- Anything your Bolta role does not allow. Viewers cannot approve or publish, and Safe Mode and client sign-off still apply on top. A network you have not connected is out of reach too.
- Can Codex in the IDE or desktop app use Bolta, or only the terminal?
- Codex's MCP docs say the ChatGPT desktop app, Codex CLI and IDE extension share this configuration, so the entry you add once should show up in each. We have only described the terminal commands here, so check /mcp in the one you use.
- 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.
If something does not work
Quick fixes for the common snags.
- codex mcp list does not show bolta
- The entry did not save. Re-run codex mcp add bolta --url https://mcp.bolta.ai/mcp, or check that [mcp_servers.bolta] and the url line are in ~/.codex/config.toml, then start a new session.
- Codex says the command is not found
- Command names can change between Codex versions. Update Codex, or check the MCP page in Codex's official docs for the current wording.
- The sign-in page does not open
- You may be on a machine with no browser. Run codex mcp login bolta --no-browser, open the printed link elsewhere, and paste the full address you land on back into the terminal.
- 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.
- It saved a draft but nothing was posted
- That is the design. A saved draft waits for your yes. Approve the exact text in Bolta or in chat, and only then will it get a time or go out.
Ready to schedule social media posts with Codex?
Connect Codex and ask for your first draft. Nothing goes out until you say yes.