Loading...
×Use the Kimi Code CLI with Tareno to turn a debugging session into a LinkedIn explanation of the symptom, the real cause and how it was confirmed, with secrets removed and a draft you approve.
Yes, after Tareno is added as a remote MCP server. Kimi Code summarises the symptom, the real cause, the confirmation and a check for similar code, and saves the draft through Tareno. It cannot tell which details are confidential, so you remove them, and a time request stays pending until you approve it.
Last reviewed 2026-10-25 · Markdown version for AI agents
The best technical posts are written the day the bug dies, while the false leads are still vivid. Two days later the story shrinks to the fix. A command-line agent that sat through the session can still reconstruct the reasoning from the history: what looked wrong, what was actually wrong, how the cause was confirmed. Kimi Code can draft that account and Tareno can keep it as a draft until you have cleaned it. This page follows a backend developer who spent an afternoon on a timezone bug. It treats the removal of secrets as a step of its own, because session history is full of paths, hostnames and tokens that must not reach a public post. Tareno has not completed a client test with Kimi Code.
Imagine a developer whose reports showed the wrong day for users near midnight. After the fix, she asks Kimi Code to summarise the session for other engineers. It drafts a LinkedIn post: the symptom, the false lead about caching, the real cause in a date conversion that dropped the offset, how a failing test confirmed it, and one thing to grep for in similar code. She removes a staging hostname and a path with her username. Kimi Code confirms her profile with list_accounts and saves the approved text with create_drafts.
Add Tareno as a remote HTTP server as the Kimi Code overview describes, sign in with OAuth, then ask for list_accounts. Your LinkedIn profile in the answer is the check; an empty answer means it has to be connected inside Tareno.
Ask Kimi Code for the symptom, the false leads, the real cause and the confirmation, in that order. The false leads are what make the post useful, since other engineers will follow the same ones.
Open the fixed lines and the test that confirms them. A narrative that sounds right can still blame the wrong line, so check that the post matches the commit.
Search the draft for hostnames, usernames in file paths, stack-trace frames from internal modules, keys and tokens. Kimi Code reads the whole session and may have copied any of them.
Kimi Code confirms your profile through list_accounts and files the cleaned text with create_drafts, giving you a draft ID. Scheduling has not happened yet.
Tell it the day, the time and an IANA zone. schedule_posts returns a pending action that stays 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 one you would use for a technical explanation on LinkedIn, and say clearly if you cannot reach Tareno.From this session, list the symptom, each false lead we followed and why we dropped it, the real cause with the file and function, and the test that confirmed the fix. Mark anything you inferred rather than saw. Do not write the post yet.Write a LinkedIn post of about 200 words for other engineers from that story, ending with one concrete thing to search for in similar code. Leave out stack traces, hostnames, usernames in paths and any key or token, and say so if you removed something.Use Tareno to confirm my LinkedIn profile [name] and save the approved explanation as one 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 [Tuesday 08: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: Microsoft Learn: LinkedIn Posts API, 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:
It works from the conversation and the repository state available to it, which may not include everything you tried. Ask it to mark inferences, and fill in the false leads it missed from your own memory before the draft is saved.
Search the draft for hostnames, paths with usernames, keys and tokens, and read it once as a stranger would. Do not rely on the agent to catch them, because it has no way to know what your organisation treats as sensitive.
One or two lines, if they carry the point, such as the conversion that dropped the offset. LinkedIn does not format code, so a long block reads badly and invites copy errors. Link to a public gist if more is needed.
It is the minimum: `list_accounts` should show your profile. Moonshot documents the connection and Tareno has not finished a client test, so save one harmless draft and open it in Tareno before you write about a real bug.
LinkedIn requires a role such as administrator for the connecting member before a page can be posted for. Once that is granted in Tareno, the page shows up in `list_accounts`; editing the prompt cannot fix a missing role.
Yes: the pending request in Tareno is that check. Nothing at all reaches LinkedIn until you approve it there yourself, and `get_action_status` reports afterwards what LinkedIn answered, including any refusal.