Threads 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 Threads 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.
Read the top entry in CHANGELOG.md and draft a Threads post about it under 500 characters
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 Threads
Threads caps a post at 500 characters, and Bolta handles longer text by splitting it into a thread of connected posts, so one long idea does not fail.
- Text posts, and posts with images.
- A carousel of 2 to 10 items.
Threads 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 Threads from Kimi K3: Polls on Threads. Not confirmed for Bolta. Mirroring a Threads post onto Instagram. Threads does not do that on its own, and this page does not confirm that Bolta does it.
| What to know | Threads's own rule | What Bolta does |
|---|---|---|
| Post length | A single Threads post is capped at 500 characters, and a reply carries the same limit. | Bolta uses 500. Longer text is split into a thread of connected posts. |
| Media | A post can carry up to 20 photos or videos in one carousel. Video is limited to 5 minutes and 1 GB. | A carousel in Bolta takes 2 to 10 items. An image over 8 MB is shrunk if Bolta can. |
| Links | Links are allowed, show as a preview card, and are capped at 5 per post. | Each Threads link is swapped at publish time for a short Bolta link that counts clicks. If the swap fails, the link goes out as written. |
| Continuing past the limit | You can continue by replying to your own post, which keeps the follow-on in the same chain. | Send a long text as several parts and Bolta posts every part after the first as a reply, which keeps them in one chain. |
| Formatting | Not stated on this page. | Plain text only on Threads. Markdown is flattened, and tags and mentions stay as typed. |
Kimi K3 jobs for Threads, and how to write them
- Summarise this week's git log into an update for your build-in-public audience
- Keep one repo per brand by using a project-level .kimi-code/mcp.json
- Write one longer text when you want a thread, and read where it splits before you say yes.
Example prompts for Threads
Things to type in Kimi K3. Each one asks for a draft and shows you the text first.
Read the top entry in CHANGELOG.md and draft a Threads post about it under 500 characters
List my Bolta brands and the accounts connected to each
Turn the release notes into one longer Threads text that Bolta can split into a thread, and show it to me
What is waiting for my yes in Bolta?
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Kimi K3 asks Bolta for the Threads post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On Threads the exact text includes where a long text is split into a thread and the topic tag, so read each 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 Threads
Parts of this route are not confirmed. The note above says which.
For Threads, 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 Threads account itself is connected inside Bolta, not in Kimi K3.
Kimi Code CLI is a terminal agent from Moonshot AI, so a Threads 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: What is waiting for my yes in Bolta? The reply goes along these lines: Three items are waiting: two post drafts and one reply. Nothing has been approved or sent. Want me to read the drafts back to you? Read only. Nothing changes.
A run in CI or on a server cannot open a browser, so use a Bolta API key. Create it in Bolta under Settings, then API Keys. Keys start with bolta_sk_.
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.
The MCP connection works without it. Other agents on the same machine that read ~/.agents/skills can share the same copy.
- Weekly routines. Describe a cadence such as one release-notes post every Friday. Kimi shows the plan, you confirm it, and it is saved switched off until you turn it on separately.
- 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.
- 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.
- Check the posting rules. Bolta returns the length and format limits for the chosen network, which matters when a long CHANGELOG.md is the source.
- Setup: Check the connection. Run /mcp and look for bolta shown as connected. If sign-in will not complete, create a key in Bolta under Settings, then API Keys (it starts with bolta_sk_), put it in an environment variable, and set bearerTokenEnvVar on the bolta entry to that variable name.
- Setup: Read before you write. In a new session ask: What is waiting for my yes in Bolta? It should list your real brand and change nothing.
- Skill via npx skills add. Kimi scans ~/.agents/skills for SKILL.md folders. We have not checked whether the installer lists Kimi, so copy skills/bolta into that folder if it does not.
- A post you approved and scheduled in Bolta publishes at its time without Kimi or your machine.
- Browser sign-in. Choose this when you are working at your own machine. Run /mcp-config login bolta, approve in the browser and tick the brands. No secret sits in a file. This is the route we expect to work, but it has not been tested end to end in Kimi Code.
Connect Kimi K3 to Bolta
Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.
Threads questions, answered for Kimi K3
- What does Bolta do when Kimi K3 writes more than 500 characters for Threads?
- Bolta splits longer text into a thread of connected posts, and the 500 limit also applies to each image caption. The parts are posted as replies in order, so read where the splits fall before you say yes.
- Can Kimi K3 reply to someone else's Threads post?
- Yes, from a public link (reply-to-social-content). The agent writes the text first with the voice-aware draft tool (draft-engagement-reply) (for a stored opportunity) or (draft-inbound-reply) (for a comment on your own post), shows it to you, and calls reply-to-social-content only after your yes, because that call posts the reply. Finding conversations to join (search-engagement-opportunities) needs a campaign already attached to the account.
- Is Kimi K3 the same as Kimi Code?
- No. Kimi Code CLI is the terminal agent that Bolta connects to. K3 is reported to be a Moonshot AI model, but we could not confirm from an official Moonshot page that it exists in the form reported or which model Kimi Code uses by default.
- Can Kimi read my whole repo and post about it?
- Kimi can read the files you point it at, such as CHANGELOG.md, a README or git log output, and write from them. It only saves drafts to Bolta. What you approve is a separate step, so check that a draft does not leak internal details before saying yes.
- What should I do if /mcp shows Bolta but Kimi cannot see any brands?
- Sign in again with /mcp-config login bolta and make sure you ticked at least one brand. A connection reaches one organization, so also check that you are signed in to the right one in the browser.
- 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.
- Does Kimi K3 publish Threads posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that Threads 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.
Threads from other AI agents
The same Threads limits apply whichever agent asks. The connection and the setup are what change.
Try a Threads draft from Kimi K3
Connect Kimi K3, ask for a Threads draft and read the exact text. Nothing goes live until you say yes.