Loading...
×Use GitHub Copilot in VS Code with Tareno to turn a release's merged pull requests into thank-you posts for X within 280 characters, with handles checked, approved by you in Tareno.
Yes, once Tareno is added as an MCP server in VS Code. In agent mode Copilot reads the merged pull requests, names the contributors with what they changed, writes posts within 280 characters and saves drafts through Tareno. Tareno has not completed a client test for Copilot, so setup follows published documentation. Approval happens in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
Open-source projects run on people who rarely get thanked in public. A release is the natural moment, and the pull request list already says who did what. The work is turning that list into posts that sound like a person wrote them, with the right handle next to the right name. Copilot can read the merged pull requests in the repository and phrase the thanks; Tareno saves the drafts. This page follows the maintainer of a mid-sized library through a release, with the Copilot setup steps documented by GitHub and VS Code, and with the rule that nobody is tagged unless the maintainer is sure of the handle and that they would welcome it.
Imagine a maintainer who has just released version 4.1 of a library with fourteen merged pull requests from nine contributors. In VS Code she switches Copilot to agent mode and asks it to group the pull requests by contributor and pick the five most substantial. Copilot reads titles, descriptions and diffs, and reports that one pull request was written by two people. It drafts five thank-you posts within 280 characters, each naming what the person fixed in plain words. Handles come from the contributors' GitHub profiles, which she checks. She saves the drafts with create_drafts and requests five slots over the week.
On Copilot Business and Enterprise, GitHub says an administrator must switch on the MCP servers policy. When the option is absent, ask them; there is no sensible way around it.
Put a remote entry of type http with the hosted address into the workspace mcp.json, or run the Add Server command. Guides mention a browser sign-in the first time it is used.
In agent mode, ask Copilot for list_accounts. Your X account in the reply means the server works; if it is missing, connect it in Tareno.
Ask Copilot to list the merged pull requests of the release grouped by author, with a one-line description of what each changed. Contributors thanked for the wrong change notice immediately.
Copilot can see GitHub usernames, but a person's X handle may differ or not exist. Verify each handle yourself, and leave out anyone who would rather not be tagged.
Copilot writes the posts within 280 characters and saves them through create_drafts. Give days, times and an IANA time zone, and approve the pending requests in the Tareno dashboard.
List the pull requests merged between [v4.0.0] and [v4.1.0], grouped by author, with a one-line description of what each changed and whether the change fixes a bug, adds a feature or improves docs. Mention any pull request with more than one author.From that list pick the five contributions that most affect users, and tell me why for each. Do not rank by number of lines changed, and mark any contributor whose X handle you cannot find in the repository so I can look it up myself.Write five X thank-you posts for Tareno drafts, each within 280 characters, naming the contributor and saying in plain words what their change did for users. Use no handles that I have not confirmed, and avoid generic phrases such as huge thanks to everyone.Use Tareno to confirm the X account [project handle] and save the five approved posts as drafts. After I confirm, ask for one slot a day at [10:00] in the [Europe/Berlin] time zone and return the pending action IDs.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_accountsNot yet; no client test has been completed. The VS Code setup follows published documentation, so run a read-only call first and only then trust it with drafts for a release you are announcing.
MCP tools belong to agent mode. Switch to it, look for the Tareno tools in the tool list and make the first call a harmless one.
It cannot reliably. It sees GitHub usernames and any links in profiles, but the X handle may differ or be absent. Look each one up yourself and tell Copilot only the ones you have confirmed.
Only if you are sure of the handle and the person would welcome it. A thank-you post that names the person and the change works without a tag, and Copilot can write it either way.
Because a long list does not fit in 280 characters, and Tareno cannot save threads for X. Five posts across a week also keep the release visible longer than one post on the day.
No. A scheduling request becomes a pending action in Tareno. X receives the post only after you approve it in the dashboard, and Copilot can only report that it is pending.