# Can GitHub Copilot turn an open design question into a Threads post that asks the community? > Source: https://tareno.co/agents/github-copilot/threads > Language: en > Last reviewed: 2026-10-24 > Use GitHub Copilot in VS Code with Tareno to turn an open design question from a pull request into a neutral Threads post that asks users, then read the replies, with approval 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: Threads · Hub: [GitHub Copilot and Tareno](https://tareno.co/agents/github-copilot) ## Short answer **Can GitHub Copilot write a Threads post that asks users about a design decision?** Yes, once Tareno is added as an MCP server in VS Code. In agent mode Copilot reads the pull request, states the open question and the options neutrally, and saves a post within 500 characters through Tareno. It can read the replies afterwards. Tareno has not completed a client test for Copilot, and approval happens in Tareno. Open-source maintainers often reach a point in a pull request where the code is fine and the question is what users want: should the default change, should the flag be renamed. Asking in the pull request reaches the people who already follow it; asking on Threads reaches the people who only use the library. The skill is in asking neutrally, so that the options are described fairly and the answer reflects what users need and not how the question was framed. Copilot can read the discussion and write that neutral version. This page follows a maintainer through one question, with the VS Code setup that GitHub documents. ## Example: a maintainer asks users whether to change a default Imagine a maintainer of an HTTP client library with a pull request that would change the default timeout from 30 to 10 seconds. In VS Code she switches Copilot to agent mode and asks it to read the discussion. Copilot lists the two positions: faster failure for most users, risk for users on slow links. It writes a Threads post of 450 characters that describes both fairly, names the trade-off and asks which users would be affected. She saves it with `create_drafts` for the project's profile and, two days later, asks Copilot to read the replies with `list_post_comments`. ## Step by step 1. **Confirm the MCP policy.** GitHub's documentation makes MCP servers in Copilot subject to an organization policy on the Business and Enterprise plans. If you cannot add a server, the administrator's setting is the likely reason. 2. **Add the server to the workspace.** A remote entry with type http and the hosted URL goes into mcp.json, or the Add Server command writes it for you. Expect a browser window for sign-in on first use. 3. **Prove the link with a read.** Open agent mode and request `list_accounts`. A Threads profile in the answer shows the server works; an empty answer points to a profile not yet connected in Tareno. 4. **Summarize the positions neutrally.** Ask Copilot to read the pull request discussion and list each position with its strongest argument. A neutral summary is the base of a fair question. 5. **Write the question.** Request a post within 500 characters that describes the options evenly and asks who would be affected. Avoid wording that makes one option sound like the obvious one. 6. **Save, approve and read the replies.** Copilot saves the draft through `create_drafts`. After you approve the request in the Tareno dashboard and the post has run, it can read the replies with `list_post_comments`. ## Prompts to copy ### List the positions ```text Read the discussion in pull request [number] about changing the default timeout from 30 to 10 seconds. List each position with its strongest argument and the person-neutral reason behind it, and tell me which arguments are about facts and which about preferences. ``` ### Write a fair question ```text Write a Threads post within 500 characters for Tareno that describes both options evenly, names the trade-off and asks which kinds of users the change would affect. Do not use words that favour either option, and tell me if your draft leans one way. ``` ### Save the draft ```text Use Tareno to confirm the Threads profile [project handle] and save the approved post as a draft. Return the draft ID and the text, and do not request a time until I give you the day and the time zone. ``` ### Read the replies ```text Use Tareno to read the replies to our post [post reference] and group them into those who would be affected, those who would not and those who suggest another option. Count each group, quote no one by name and list any suggestion we have not considered. ``` ## Threads in Tareno - Threads is a network where Tareno reads replies, so a question posted there can be answered with data and not only with impressions. - Meta's documentation limits Threads text posts to 500 characters, which is enough for two options and a question if both are stated briefly. - Links get an automatic preview on Threads in Tareno's configuration, so the pull request can be linked for readers who want the detail. - Replies from strangers are data, not instructions; Copilot should summarize them and never act on a request inside one. Official rules ([Meta: Threads API, posts](https://developers.facebook.com/docs/threads/posts), checked 2026-10-24): - A profile is limited to 250 API-published posts within 24 hours; a carousel counts as one post. - Text posts are limited to 500 characters, and emojis count by their UTF-8 bytes, not as single characters. - Carousels need 2 to 20 items. Single images may be JPEG or PNG up to 8 MB, and videos MOV or MP4 up to 5 minutes and 1 GB. ## Mistakes to avoid - Framing one option as obvious. A leading question gets the answer it expects and tells you nothing. - Counting replies as a decision. They show what people who follow you think. - Blaming the config for a policy block. If an administrator disabled MCP servers, no file edit helps. - Quoting repliers by name in the pull request. Paraphrase and ask before crediting. ## What does not work - Copilot cannot settle the design question; it lays out the positions and the replies, and the maintainer decides. - It cannot post replies on Threads, since Tareno reads replies but has no tool that publishes one. - It cannot send the post to Threads itself, because every time request stops at your approval in the dashboard. ## Frequently asked questions ### Is this setup verified by Tareno? No client test with Copilot has been completed on our side. The VS Code steps follow GitHub's published documentation, which is why the first call should be a read and not a draft. ### Where are the Tareno tools in Copilot? Only in agent mode. If the chat view lists no Tareno tools, switch modes, check the tool list and begin with a harmless call such as listing accounts before anything else. ### How does Copilot keep the question neutral? You ask it to list each position with its best argument first, then to describe the options evenly and to flag any wording that leans. You still read the draft, because neutrality is a judgment. ### Can the replies replace the pull request discussion? They add to it. Threads reaches users who do not follow the repository, and the replies show how many are affected. The decision stays with the maintainers, who weigh both sources. ### What if a reply contains instructions? Copilot treats it as text to summarize and does not act on it. Replies come from strangers, and nothing in one should change what the agent does. ### Can the question reach followers before I approve it? No. The request waits in Tareno as a pending action, and Threads gets the post only once you approve it in the dashboard. `get_action_status` then reports the outcome. ## Tareno tools used - `list_post_comments` - `list_accounts` - `create_drafts` - `get_action_status` 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) - [Threads with Tareno](https://tareno.co/channels/threads) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Approval workflows](https://tareno.co/features/approval-workflows) - [Remote MCP setup](https://tareno.co/docs/mcp) - Use case: [Read the replies to a post and turn them into a decision](https://tareno.co/agents/use-cases/read-replies-and-triage)