LinkedIn posts with Muse and Bolta
Queue social posts from Muse Code, Meta's terminal agent. Parts of the Muse 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
This is the Muse Code path. We have not confirmed a way to add Bolta in the Muse app or from WhatsApp.
Draft a LinkedIn post announcing our v2.0 release, using the notes in CHANGELOG.md, and save it for my review
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 Muse
- Confirmed in Meta's Muse Code docs: remote MCP servers over streamable_http, an mcp_servers block in ~/.config/muse/settings.json, and OAuth sign-in with muse mcp login.
- Not confirmed: that the Muse app (phone, desktop or WhatsApp) accepts a Bolta MCP link. Meta says the app has custom connectors, but we could not read the steps.
- Not tested end to end: nobody has run a full draft, review and schedule round trip through Muse Code with Bolta yet.
- Not confirmed: how to send an API key in the headers field, and whether the optional Bolta skill shows up in muse skills list.
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 Muse: 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. |
Muse jobs for LinkedIn, and how to write them
- Draft a week of posts in your brand voice, then review them in Bolta rather than in the shell
- Set up a weekly routine that drafts posts for your review, then close the terminal
- 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 Muse. Each one asks for a draft and shows you the text first.
Draft a LinkedIn post announcing our v2.0 release, using the notes in CHANGELOG.md, and save it for my review
Read CHANGELOG.md and draft a LinkedIn post about the v2.0 release. Save it for my review.
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
Muse 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 Muse for LinkedIn
Parts of this route are not confirmed. The note above says which.
For LinkedIn, Muse, from Meta, reaches Bolta through mcp_servers entry in the Muse Code settings file (streamable HTTP). Sign-in: Sign in (OAuth) with muse mcp login. The LinkedIn account itself is connected inside Bolta, not in Muse.
Muse Code is Meta's terminal agent and the route this page covers. A LinkedIn draft from the Muse app on phones, desktop or WhatsApp is not confirmed, so this page does not promise it.
An illustration from the Muse guide, not real output. You ask: Read CHANGELOG.md and draft a LinkedIn post about the v2.0 release. Save it for my review. The reply goes along these lines: I read the v2.0 entry and saved one LinkedIn draft in Bolta, written in your brand voice. Here is the exact text. It is not approved or scheduled. Tell me yes when you want to go ahead. Draft saved. Waits for your yes.
An illustration from the Muse guide, not real output. You ask: What is waiting for my approval in Bolta? Read each one back to me. The reply goes along these lines: You have three items in review. I read each one back above. I have not approved or rejected anything. Say which ones you want approved and I will confirm the exact text first. Read only. Nothing changed.
~/.claude/skills, which Muse Code also looks in by default, so a skill you installed for Claude Code can be seen.
Meta's docs say you can sign in in the browser or headless but do not say how headless works. If no browser window opens, run muse mcp login bolta again, or try the Bearer key route, which is also unconfirmed.
Meta lists a headers field for streamable_http servers, and Bolta accepts a Bearer bolta_sk_ API key, so a header may work for a headless machine. We have not confirmed the exact format Muse Code expects, so check Meta's configuration page before you rely on it.
- Check the rules before drafting. Ask what a network allows, such as length or media limits, so a draft is built to fit and is not rejected later.
- Approve after your yes. Once you say yes to named drafts, Muse Code passes the content fingerprint back, so a post that changed in between is not approved by mistake.
- Your request becomes a read of your brand. For a post, Muse Code first checks your brand and voice before writing anything.
- You decide in Bolta. Review the exact text in Bolta or tell Muse Code yes. Until then nothing is approved, scheduled or published, and your role and Safe Mode still apply.
- Setup: Have a Bolta brand with an account connected. Create a Bolta account at bolta.ai and add at least one brand. Connect at least one social account to it, or Muse Code will only be able to draft.
- Setup: Open the settings file. Open ~/.config/muse/settings.json and create it if it is missing. It must contain "schema_version": 1, or Muse Code stops at startup.
- Browser extension or plain webhook. Neither is a route we document for Muse Code. The MCP entry above is the documented path.
- A routine you set up through Muse Code lives in Bolta, so it repeats while your terminal is closed.
- Muse app. Choose this only if you cannot use a terminal, and expect to wait. Meta says the app supports custom connectors, but we could not read the steps, so we do not know whether it takes a remote MCP link or which sign-in it uses. We will not tell you it works until it has been tried.
Connect Muse to Bolta
This is the Muse Code path. We have not confirmed a way to add Bolta in the Muse app or from WhatsApp.
LinkedIn questions, answered for Muse
- How long can a LinkedIn post be when it comes from Muse?
- 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 Muse should write inside the limit and show you the final text before you say yes.
- Can Muse 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.
- Can Muse publish without my approval?
- No. Bolta will not approve, schedule or publish a post until you say yes to that exact text. It refuses the request or keeps the post in review, and your role and Safe Mode still apply.
- Is it safe to connect a server to Muse Code?
- Meta's documentation says MCP tools in Muse Code are not sandboxed, so connect only servers you trust. Bolta limits the brands you tick, applies your role, and needs your yes before anything goes out.
- Has this been tested end to end?
- No. The settings format and sign-in command come from Meta's documentation, but nobody has run a full draft, review and schedule through Muse Code with Bolta. Claude Code and Codex have their own Bolta pages if you want another terminal agent.
- Muse Code stops at startup with malformed settings file
- The file must contain "schema_version": 1 and be valid JSON, with commas between entries and none at the end. Fix that and start muse again.
- Does Muse publish LinkedIn posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that LinkedIn post. Whether Muse completes the connection is not fully confirmed, so read the note above first.
More from Muse
Muse 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 Muse
Connect Muse, ask for a LinkedIn draft and read the exact text. Nothing goes live until you say yes.