# Can Kimi Code turn a changelog entry into an X post users will read? > Source: https://tareno.co/agents/kimi/x > Language: en > Last reviewed: 2026-10-25 > Use the Kimi Code CLI with Tareno to pick the user-facing entry in a changelog, write an X post within 280 characters with the version and a link, and save it as a draft you approve. ## Connection facts | Field | Value | | --- | --- | | Product surface | Kimi Code (kimi) | | Available connection | Custom MCP connection | | Connection evidence | documented | | Methods | mcp | | Authentication | oauth | | Setup | [Setup guide](https://tareno.co/docs/mcp) | | Install or connect | [Open setup](https://tareno.co/docs/mcp) | | Evidence observed | 2026-10-25 | | Facts reviewed | 2026-10-25 | Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface. Agent: Kimi Code · Network: X · Hub: [Kimi Code and Tareno](https://tareno.co/agents/kimi) ## Short answer **Can Kimi Code adapt a changelog for X and save the post as a draft?** Yes, after you add Tareno to the Kimi Code CLI as a remote MCP server. Kimi Code reads the newest changelog, picks the entry that changes what a user does, writes a post within 280 characters and saves a draft through Tareno. Tareno has not completed a client test, and a time request stays pending until you approve it. Changelogs are written for people who already follow the project: terse, grouped by type, full of issue numbers. Posted as they are, they read like noise. The useful post picks one entry and says what it lets a user do. A command-line agent can do that selection because it can see the whole file and the conventions of the project, and Tareno can hold the result as a draft. This page follows the developer of a note-taking CLI through a release. It covers the choice of entry, the rewording for a reader who does not know the internals and the check that nothing in the post was invented. The setup follows Moonshot's documentation for Kimi Code, and Tareno has not completed a client test. ## Example: the author of a note-taking CLI announces version 0.9 Imagine a developer whose 0.9 changelog lists eleven entries. She asks Kimi Code to read CHANGELOG.md and pick the one entry that changes what a user does. It chooses the new export command for Markdown folders, not the dependency bumps. It writes a post with the version and a link, and tells her which entries it left out. She checks the example command in the post by running it. Kimi Code confirms her X account with `list_accounts` and saves the text with `create_drafts`. She decides on a time in the Tareno dashboard. ## Step by step 1. **Connect Tareno and test with a read.** Add Tareno as a remote HTTP server as the Kimi Code overview describes, sign in with OAuth, then ask for `list_accounts`. Your X account in the answer is the check; an empty answer means X has to be connected inside Tareno. 2. **Let it read the whole entry list.** Ask Kimi Code to read the newest section of the changelog and to rank the entries by how much they change what a user does, with a reason for each of the top three. 3. **Choose one entry yourself.** Pick the entry. The agent proposes, but you know which change your users asked for, so the choice is yours and the other entries wait for another post. 4. **Reword for a newcomer.** Ask for a post of up to 280 characters that explains the benefit without issue numbers or internal terms. If the post contains a command, run it yourself before it is saved. 5. **Store it as a draft.** Kimi Code checks the account via `list_accounts` and files the approved wording through `create_drafts`, which returns a draft ID. Nothing is queued. 6. **Choose the moment.** Say which day, time and IANA zone you want. The pending action created by `schedule_posts` waits in the dashboard until you release it. ## Prompts to copy ### Check the connection ```text Use Tareno to list my connected social accounts with platform and account name. Read only: do not create, schedule or publish anything. Tell me which account you would use for a changelog post on X, and say clearly if you cannot reach Tareno. ``` ### Rank the entries ```text Read the newest section of CHANGELOG.md and rank the three entries that most change what a user does, with one sentence each on why. Ignore dependency updates and refactors unless they change behaviour, and do not write a post yet. ``` ### Write the post ```text Write an X post within 280 characters about entry [number 1] for a reader who does not know the internals. Include the version [0.9] and the link [release URL], leave out issue numbers and hashtags and, if you show a command, copy it exactly from the changelog. ``` ### Save the draft ```text Use Tareno to confirm my X account [handle] and save the approved post as a draft. Return the draft ID and the text, and request no time until I give you the day and the time zone. ``` ### Request the slot ```text Take the draft [draft ID] and ask Tareno to schedule it for [Thursday 10:00] in [Asia/Singapore]. Return the action ID and remind me that the request still waits for my approval in the Tareno dashboard. ``` ## X in Tareno - The release link and an example command both count against the 280 characters in Tareno's configuration, so the explanation of the benefit gets what is left. - Entries you skip become posts of their own later, since there is no thread tool for X in Tareno to chain them. - X permits up to four photos per post, so a cropped terminal screenshot of the new command can sit next to the text. - Which entry users ask about afterwards cannot be learned through Tareno, because it does not expose X posts or replies. Official rules ([X API documentation: create a post](https://docs.x.com/x-api/posts/creation-of-a-post), checked 2026-10-24): - A post may include up to 4 photos, 1 animated GIF or 1 video. - The allowed video length depends on the posting account, not on the API plan: 20 minutes and 8 GB by default, 125 minutes and 16 GB with X Premium or verified status. Tareno's configuration for X stops at 140 seconds. - Quote-posting through the API requires an Enterprise plan and is not available on self-serve tiers. ## Mistakes to avoid - Posting the changelog in full. One entry, explained, beats eleven entries listed. - Including a command that was never run. Run it before the draft is saved. - Letting issue numbers into the post. Newcomers cannot use them. - Pasting a screenshot with a username or token in the prompt line. Crop it first. ## What does not work - Kimi Code cannot know which change your users asked for, so it ranks candidates and you choose. - It cannot read replies on X through Tareno, because Tareno does not expose posts or replies for X. - It cannot make the post public by itself; a time request needs your approval in the Tareno dashboard first. ## Frequently asked questions ### Why choose one entry and not a summary? Because a summary of eleven items says nothing about any of them. A post about one change tells a reader what to try, and a link to the full list serves everyone who wants the rest. ### Does Kimi Code need the changelog in a special format? No. It reads the file as text, so any consistent layout works. Entries that name the user-visible effect make the ranking better, and entries that only say refactor give it little to work with. ### Should the post show a command? If the change is a command, yes, because it is the shortest explanation. Copy it exactly from the changelog or the docs and run it yourself first, since a wrong example in a release post gets quoted back at you. ### How should I test the setup before a release? Run the test command for the server, ask for `list_accounts`, then save one draft about an old release. Moonshot documents the steps, and Tareno has not yet completed a client test, so a rehearsal costs little. ### What happens to my sign-in after an upgrade? Moonshot's documentation says tokens from older versions are not migrated, so run the authorization command again if the server shows as needing it. The settings file itself, ~/.kimi/mcp.json, is unaffected. ### Who presses the final button? You do, in the Tareno dashboard, after reading the draft once more. Kimi Code can only file the request on your behalf, and `get_action_status` tells you afterwards whether X accepted the post. ## Tareno tools used - `list_accounts` - `create_drafts` - `schedule_posts` - `get_action_status` Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them. ## Related - [Kimi Code × Tareno overview](https://tareno.co/agents/kimi) - [X with Tareno](https://tareno.co/channels/twitter) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Approval workflows](https://tareno.co/features/approval-workflows) - [Remote MCP setup](https://tareno.co/docs/mcp)