Kimi K3 + Bluesky

Bluesky 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 Bluesky until you say yes.

Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.

Kimi K3Bolta connected
You

Read the top entry in CHANGELOG.md and draft a Bluesky post about it under 300 characters

Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.

Illustration. Your drafts show your real text, account and time.

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.
Bolta on Bluesky

What Bolta does on Bluesky

Bolta cuts Bluesky text at 300 characters and ends it with an ellipsis, so the useful part of a draft has to come before the limit.

  • Text posts of up to 300 characters, cut with an ellipsis beyond that.
  • Images. A video is left off, and Bolta publishes the text and any images.
Limits and format

Bluesky limits and format rules

Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.

Not promised for Bluesky from Kimi K3: Custom feeds and quote posts. Neither is confirmed for Bolta. Any Bluesky rule beyond what Bolta reports. This page states Bolta's limits, not a network rulebook.

Bluesky limits and format rules
What to knowBluesky's own ruleWhat Bolta does
Post lengthNot stated on this page.300 characters. Longer text is cut short and ends with an ellipsis.
MediaNot stated on this page.Images are posted. A video is skipped with a warning, and the text and any images still go out.
ThreadsNot stated on this page.Parts after the first are posted as replies, so they read as one Bluesky thread.
FormattingNot stated on this page.Bluesky shows plain text, so Bolta flattens markdown and leaves #hashtags and @mentions as typed.
Best practices

Kimi K3 jobs for Bluesky, and how to write them

  • Read a README or docs page and draft posts that explain one feature at a time
  • Ask what is waiting for approval in Bolta without leaving the terminal
  • Write to 300 characters yourself. The cut is blunt and ends in an ellipsis.
Prompts

Example prompts for Bluesky

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 Bluesky post about it under 300 characters

What is waiting for my yes in Bolta?

Turn the release notes into a three-part Bluesky thread and show me each part before saving

List my Bolta brands and the accounts connected to each

Review

Bolta saves a draft, you read the exact text, you say yes

  1. 01

    Bolta saves a draft

    Kimi K3 asks Bolta for the Bluesky post in your brand voice (save-post). A saved draft is never public.

  2. 02

    You read the exact text

    On Bluesky the exact text includes where the 300-character cut would fall, and which images are attached, because a video would be left off.

  3. 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.

Kimi K3 and Bolta

Using Kimi K3 for Bluesky

Parts of this route are not confirmed. The note above says which.

For Bluesky, 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 Bluesky account itself is connected inside Bolta, not in Kimi K3.

Kimi Code CLI is a terminal agent from Moonshot AI, so a Bluesky 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: 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.

In an untrusted folder Kimi asks whether to trust it before loading project servers, so answer that prompt the first time.

If you keep one user-level entry for many brands, name the brand in every prompt and ask Kimi to list workspaces first.

Kimi drafting a post and Bolta publishing it are two separate steps. Saving a draft changes nothing public, and Bolta's role checks apply no matter what a prompt says.

  • Review and approval. Ask what is waiting, then approve, reject or send a post to a teammate. Direct approval needs your yes for that exact post, and Bolta's own role checks still apply.
  • 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.
  • Save the draft. Kimi writes the text from the file or git log you pointed at and saves it as a draft. Saving does not approve, schedule or publish anything.
  • 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: Open the MCP config. Open ~/.kimi-code/mcp.json in a text editor and create it if it is missing. You can also start kimi and run /mcp-config to add a server without editing JSON. A file at .kimi-code/mcp.json inside a project overrides the user file for the same server name.
  • Bolta REST API from a Kimi shell command. The Bolta API is documented at /docs/api and a terminal agent can call it, but we have not tested that from Kimi Code.
  • 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

Connect Kimi K3 to Bolta

Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.

FAQ

Bluesky questions, answered for Kimi K3

Can Kimi K3 post a video to Bluesky?
Not through Bolta. Bolta publishes the text and any images and leaves a video off, with a warning. Use images, or post the video on another network.
What is the Bluesky length limit for posts from Kimi K3?
300 characters. Longer text is cut short and ends with an ellipsis, so write to the limit and read the final text before you say yes.
Do I need an API key to connect Bolta to Kimi?
Not if browser sign-in works for you: run /mcp-config login bolta. Bolta's sign-in has not been tested in Kimi Code, so the API key route is the fallback.
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.
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.
Bolta shows as not connected in /mcp
Run /mcp-config login bolta again and make sure you ticked at least one brand. If you use an API key, check that the environment variable is set in the shell that launched Kimi.
Does Kimi K3 publish Bluesky posts without my yes?
No. Nothing is approved, scheduled or published until you say yes to that Bluesky 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.

Bluesky from other AI agents

The same Bluesky limits apply whichever agent asks. The connection and the setup are what change.

Try a Bluesky draft from Kimi K3

Connect Kimi K3, ask for a Bluesky draft and read the exact text. Nothing goes live until you say yes.