# Can GitHub Copilot write X thank-you posts for the contributors of a release? > Source: https://tareno.co/agents/github-copilot/x > Language: en > Last reviewed: 2026-10-24 > 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. ## Connection facts | Field | Value | | --- | --- | | Product surface | GitHub Copilot (github-copilot) | | 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 | No dated observation recorded | | 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: GitHub Copilot · Network: X · Hub: [GitHub Copilot and Tareno](https://tareno.co/agents/github-copilot) ## Short answer **Can GitHub Copilot draft X posts that thank the contributors of a release?** 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. 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. ## Example: a library maintainer thanks five contributors after a release 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. ## Step by step 1. **Look at your organization's policy.** 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. 2. **Register Tareno in VS Code.** 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. 3. **Call something harmless.** 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. 4. **Group the release by person.** 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. 5. **Check handles and consent.** 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. 6. **Write, save and approve.** 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. ## Prompts to copy ### Group by contributor ```text 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. ``` ### Pick the five and explain ```text 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 the thank-you posts ```text 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. ``` ### Save and space them ```text 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. ``` ## X in Tareno - Tareno's configuration for X allows mentions inside the 280 characters, so a handle can be tagged, but a wrong handle notifies the wrong person. - X's API documentation notes that quote posts require an Enterprise plan, so reposting a contributor's own announcement with a comment has to be done by hand on X. - Tareno does not read posts or replies on X, so Copilot cannot see whether a contributor replied or whether they already announced the change themselves. - Tareno saves single posts for X, so five thank-yous are five separate posts, not a thread, and each should make sense on its own. 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 - Tagging a wrong handle. GitHub and X usernames often differ, so verify each one before the post goes out. - Thanking for the wrong change. Check that the description matches the contributor's actual pull request. - Ranking by lines changed. A one-line fix can matter more to users than a large refactoring. - Skipping the organization policy. If MCP servers are blocked for Copilot, the tools never appear. ## What does not work - GitHub Copilot cannot know whether a contributor wants to be tagged on X, so the maintainer decides and verifies each handle. - It cannot see replies or earlier posts on X through Tareno, since Tareno does not expose them for X. - It cannot publish by itself, since scheduling requests wait for your approval in the Tareno dashboard. ## Frequently asked questions ### Is Tareno tested with Copilot? Not 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. ### Why do the tools not show in ordinary chat? 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. ### How does Copilot find contributors' X handles? 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. ### Should I tag everyone I thank? 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. ### Why five separate posts instead of one list? 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. ### Does anything go live before I approve it? 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. ## Tareno tools used - `list_accounts` - `create_drafts` 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 - [GitHub Copilot × Tareno overview](https://tareno.co/agents/github-copilot) - [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)