Loading...
Kimi Code/TarenoKimi Code is Moonshot AI's command-line coding agent.
Kimi Code / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
Kimi CodeIllustrated demo · no live account
Run the kimi mcp add command with the http transport, OAuth as the authentication, a name such as tareno and Tareno's MCP address. Then run kimi mcp auth tareno to complete the browser sign-in, and kimi mcp test tareno to check it. Servers are stored in ~/.kimi/mcp.json. The steps follow Moonshot's documentation, and Tareno has not completed a client test.
Moonshot's documentation gives the form kimi mcp add with the http transport, followed by a name and the URL. For a server that signs you in, add the OAuth authentication option. Use the address shown on the right for Tareno.
Run kimi mcp auth with the server name. A browser opens for the authorization flow, and the token is saved under ~/.kimi/mcp-oauth/ for later use. Sign in with your own Tareno account, not a shared one.
kimi mcp test with the server name checks that it responds, and kimi mcp list shows what is configured. The documentation also says servers live in ~/.kimi/mcp.json, where a remote server uses a url field and optional headers.
Ask Kimi Code to call your connected accounts. The account you meant to post from appearing in the answer is the confirmation; an empty answer means that account still has to be connected inside Tareno.
"url": "https://tareno.co/api/mcp"Input
Provide the approved source and audience.
Review-ready drafts
Use Tareno and compare the returned draft IDs.
Approval in Tareno
Review text, media, account, and time in Tareno and approve.
A coding agent that has just read the changes is well placed to describe them. These jobs use that, and each has a workflow guide.
Changelogs are written for people who already use the tool and read poorly as posts. Kimi Code can take the entries, pick the one that changes what a user does and write a post within 280 characters that links the full list, leaving the other entries for the next post you decide to write.
After a long debugging session the reasoning is fresh: what looked wrong, what was wrong, how it was confirmed. Kimi Code can turn that into a LinkedIn explanation for other engineers, with the stack trace and any secrets removed, so a lesson that would be forgotten by Friday becomes a draft.
Moonshot's documentation lists AGENTS.md memory, permission modes, hooks and skills for the CLI. A team can keep its rules for public posts, such as no customer names and a limitation in every case study, in AGENTS.md so that every session starts from them.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
Codex, Claude Code and Grok Build also run in the terminal and reach Tareno as remote MCP servers. Kimi Code's own commands for adding, authenticating and testing a server are the main difference, along with its AGENTS.md and skills support. Choose it if it is already your daily tool, and keep a read-only check in your routine either way.
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:
The Kimi Code CLI, Moonshot AI's command-line coding agent. It makes no statement about the Kimi chat app or about any specific model, because the documentation it relies on describes the CLI's MCP client rather than model capabilities.
In ~/.kimi/mcp.json, according to Moonshot's documentation. A remote server uses a url field, with an optional headers object for values such as API keys. OAuth tokens are kept separately under ~/.kimi/mcp-oauth/ after you authorize.
Add the server with OAuth as the authentication, then run kimi mcp auth with the server name. A browser opens, you sign in with your own Tareno account, and Kimi Code saves the token so later sessions do not ask again.
Run kimi mcp test with the server name, then ask for `list_accounts` in a session. The first checks the transport and the second confirms that Tareno returns your accounts, which is the check that matters before any draft is saved.
Not yet. The steps follow Moonshot's documentation, and Tareno's OAuth is standard, but a full read-only run through Kimi Code has not been completed. Treat your first `list_accounts` call as the test for your own setup.
No. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches X or LinkedIn until you approve it in the dashboard. Kimi Code can only report that the action is pending and read its status afterwards.
Prefer OAuth. A key placed in a header is stored in the config file as written and can end up in backups or screenshots. The sign-in flow keeps the credential in Kimi's token store and ties it to your own account.
Usually `list_accounts` to confirm the destination, then `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything, and `get_action_status` tells you what became of the request.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.