Loading...
×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.
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.
Last reviewed 2026-10-25 · Markdown version for AI agents
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.
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.
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.
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.
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.
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.
Kimi Code checks the account via list_accounts and files the approved wording through create_drafts, which returns a draft ID. Nothing is queued.
Say which day, time and IANA zone you want. The pending action created by schedule_posts waits in the dashboard until you release it.
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.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 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.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.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.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: X API documentation: create a post, read on 2026-10-24. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
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.
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.
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.
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.
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.
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.