X (Twitter) posts with Kimi K3 and Bolta
Turn changelogs and git history into social drafts from the Kimi Code terminal. Parts of the Kimi K3 route are not confirmed yet, and the note below says which. Nothing goes live on X until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.
Use git log from the last 7 days and draft three posts for X
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 Kimi K3
- Confirmed in Kimi's own docs: Kimi Code CLI loads remote HTTP MCP servers from mcp.json, accepts static headers and a bearerTokenEnvVar, and can run a browser sign-in with /mcp-config login.
- Confirmed in Kimi's own docs: skills are folders with a SKILL.md, read from ~/.agents/skills among other places.
- Not tested: Bolta's browser sign-in has not been run end to end inside Kimi Code. If it does not complete, use the Bolta API key route below.
- Not confirmed: the Kimi chat app at kimi.com and any official Kimi plugin. This page is about the Kimi Code terminal agent only.
- Not confirmed: Kimi K3 and which model Kimi Code runs by default. We have not checked an official Moonshot page for either, so the name is used here only because people search for it.
What Bolta does on X
Bolta reads the limit for each connected X account, so a Premium account and a free account get different ceilings. Text that is too long does not get trimmed on X: the post fails, so the draft has to fit first.
- Single posts and threads. In a thread, Bolta posts every part after the first as a reply to the one before.
- Images. A post needs text: an image with no text is not supported on X.
X 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 X from Kimi K3: Polls and Spaces announcements. Neither is confirmed for Bolta. How many hashtags work best. Bolta checks none, and this page makes no claim about it.
| What to know | X's own rule | What Bolta does |
|---|---|---|
| Post length | Accounts without a paid subscription are limited to 280 characters. X Premium subscribers can publish up to 25,000. | Bolta reads the limit per account. Longer text makes the post fail, so shorten it first. The 25,000 limit is a ceiling for Premium accounts, and X can still refuse a long post. |
| Links and media | A pasted link counts as 23 characters however long it is. Photos, videos and GIFs count as zero characters. | Bolta does not check how many hashtags you use or their format. They are kept as typed. |
| Threads | Posts can be chained into a thread, and each post carries its own separate character limit. | Each X thread part after the first is posted as a reply to the one before it. |
| Who can reply | Replies can be limited to everyone, accounts you follow, verified accounts, or only the accounts you mention. It is chosen before you post. | The default is that anyone can reply unless you limit it. |
| Video | Not stated on this page. | Video on X is checked on X's side for duration, format and posting eligibility, so a successful upload does not guarantee publication. Ask for the posting rules before you attach one. |
Kimi K3 jobs for X, and how to write them
- Turn a release's CHANGELOG.md into a launch post and a short follow-up thread
- Read a README or docs page and draft posts that explain one feature at a time
- Write to 280 unless the account has X Premium. Check the count, because a post over the limit fails instead of being cut.
Example prompts for X
Things to type in Kimi K3. Each one asks for a draft and shows you the text first.
Use git log from the last 7 days and draft three posts for X
Use git log for the last 7 days and draft three posts for X.
Read the top entry in CHANGELOG.md and draft an X post about it that fits in 280 characters
Look at the newest tagged release and draft an X post with a link to it
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Kimi K3 asks Bolta for the X post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On X the exact text includes the character count with links counted at 23, and, for a thread, every part in order.
- 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 Kimi K3 for X
Parts of this route are not confirmed. The note above says which.
For X, Kimi K3, from Moonshot AI, reaches Bolta through Remote MCP server in mcp.json (Kimi Code CLI). Sign-in: Sign in (OAuth) or Bolta API key. The X account itself is connected inside Bolta, not in Kimi K3.
Kimi Code CLI is a terminal agent from Moonshot AI, so an X draft can start from your README, changelog or git log. The Kimi chat app is not covered here.
An illustration from the Kimi K3 guide, not real output. You ask: Use git log for the last 7 days and draft three posts for X. The reply goes along these lines: I grouped the week's commits into three themes and saved three short drafts. None are approved or scheduled. The third is the weakest, so I flagged it for you to edit or drop. Drafts saved. Wait for your yes.
An illustration from the Kimi K3 guide, not real output. You ask: Show me what the Friday release-notes routine did last week. The reply goes along these lines: I pulled its recent runs. I can tell you whether each run drafted a post and where it went for review. I have not changed the routine. Read only. Nothing changes.
A .kimi-code/mcp.json inside a project stays disabled in a headless run (for example kimi -p) unless that folder is already trusted, because Kimi cannot show its trust prompt there. Keep the bolta entry in the user file, ~/.kimi-code/mcp.json, for CI.
Kimi Code reads skills from folders with a SKILL.md, including ~/.agents/skills. The Bolta skill adds guidance on how to use the tools well, such as checking posting rules before saving a post.
In an untrusted folder Kimi asks whether to trust it before loading project servers, so answer that prompt the first time.
- Launch campaigns. For a bigger release, Kimi can plan a short campaign around one source such as a docs page, so the launch posts are drafted together.
- Results. Ask how last month's posts did on an account and draft the next one from the best performer. Reads only, nothing changes.
- Find the brand and its accounts. Kimi asks Bolta which organizations and brands your sign-in covers, then which social accounts hang off the brand you picked.
- Read your voice. Kimi pulls the brand's voice context so a changelog entry reads like your company wrote it, not like release-note boilerplate.
- Setup: Install Kimi Code CLI and open it. Install Kimi Code CLI from the official Kimi Code docs and sign in. Open it in a terminal and run kimi --version to confirm it starts.
- Setup: Add the bolta entry. Add {"mcpServers":{"bolta":{"url":"https://mcp.bolta.ai/mcp"}}} and keep any servers already in the file. Leave out the transport field: Kimi treats a url entry as HTTP.
- Hosted MCP with a Bolta API key. Kimi's docs allow static headers and a bearerTokenEnvVar on a url entry, and Bolta accepts a key on its hosted server, so it should work. We have not run it from Kimi Code. Create the key under Settings, then API Keys, and name the environment variable that holds it.
- Drafts Kimi saved stay in your Bolta inbox until someone reviews them.
- Bolta API key. Choose this for CI, a server or any run with no browser. Create a key in Bolta under Settings, then API Keys. Export it as an environment variable and name that variable in bearerTokenEnvVar on the bolta entry, so the key never sits in the JSON.
Connect Kimi K3 to Bolta
Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.
X questions, answered for Kimi K3
- What happens if Kimi K3 writes an X post that is too long?
- The post fails. Bolta does not trim X text, so Kimi K3 has to shorten it first. The limit is 280 characters for accounts without a paid subscription, and X Premium accounts can post up to 25,000, though X can still refuse a long post.
- Can Kimi K3 write an X thread?
- Yes. Ask for several parts, and Bolta posts each part after the first as a reply to the one before it, so they read as one thread. Each part carries its own limit. You read all of the parts in Kimi K3 and say yes before any of them goes out.
- Where does Kimi Code keep MCP settings, and can I set them per project?
- In ~/.kimi-code/mcp.json for all projects, or .kimi-code/mcp.json inside one project. The project file overrides the user file for the same server name.
- Will scheduled posts still go out after I close Kimi?
- Yes. Once you approve a post in Bolta, Bolta schedules and publishes it. It does not need Kimi or your terminal to stay open.
- I edited mcp.json but Kimi does not show Bolta
- Servers added mid-session only show in a new session. Close Kimi, start it again, then run /mcp to see the list. Also check that the JSON is valid and that bolta sits under mcpServers.
- A project file is ignoring my user config
- A .kimi-code/mcp.json inside the project overrides the user file for the same server name. Remove or rename the project entry, or fix the url there. In an untrusted folder Kimi asks whether to trust it before it loads project servers, so answer that prompt.
- Does Kimi K3 publish X posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that X post. Whether Kimi K3 completes the connection is not fully confirmed, so read the note above first.
More from Kimi K3
Kimi K3 can work with the other networks Bolta publishes to. Each page has its own limits and review notes.
X from other AI agents
The same X limits apply whichever agent asks. The connection and the setup are what change.
Try an X draft from Kimi K3
Connect Kimi K3, ask for an X draft and read the exact text. Nothing goes live until you say yes.