Loading...
×Use Codex with Tareno to post a feature vote on Threads, read the replies and count them with a small script that counts each person once, with approval in Tareno.
Yes. Codex writes the vote post within 500 characters, saves it as a draft through Tareno, and later reads the replies and tallies them with a small script that counts each person once. Threads has no poll feature in Tareno, so votes are replies. Scheduling stays pending until you approve it in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
Asking users what to build next is a good habit, and Threads is a natural place to ask because people answer there. The trouble is counting. Without a poll feature, votes arrive as replies in many forms: a letter, a feature name, a sentence of explanation, a second vote from the same person. Codex is good at the small, boring script that turns that mess into numbers, and at saying where the script is unsure. This page follows the maintainer of an open-source note-taking app through a vote on three features, with the counting rules that keep the result honest and the caution that a reply count is a signal, not a mandate.
Imagine a maintainer with three candidates: offline sync, tags and a dark theme. Codex drafts a post of 280 characters that asks users to reply with A, B or C, and saves it with create_drafts for the project's Threads profile. Two days after it is live she asks Codex to read the replies with list_post_comments. It writes a script that takes the first valid vote per person, reads a letter, a feature name or a clear sentence, and sets unclear replies aside. The tally shows 41 for sync, 23 for tags and 12 for the theme, with nine replies it could not classify, which she reads herself.
Choose three options at most and decide how people vote, for example by replying with a letter. Fewer options and one rule produce replies a script can read.
Codex writes a post within 500 characters that names the options and the voting rule. Meta counts emojis by bytes, so keep decoration minimal.
Codex confirms the profile with list_accounts and saves the draft through create_drafts. Give a day, a time and an IANA time zone, and approve the pending request in the Tareno dashboard.
After a day or two, Codex reads the replies with list_post_comments. Threads is a network where Tareno reads replies, which is why this poll-by-replies design works here.
Ask Codex for a small script that counts one vote per person, recognizes a letter or a feature name, sets unclear replies aside and prints the totals and the unclassified list.
Review the unclassified replies yourself. Some will be good ideas you did not offer, and those are worth more than the count.
Write a Threads post within 280 characters that asks users of my note-taking app to vote for the next feature by replying with A, B or C: A offline sync, B tags, C dark theme. State that only the first vote per person counts, and add no emojis.Use Tareno to confirm my Threads profile [project handle] and save the approved vote 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.Use Tareno to read the replies to the vote post and write a small script that counts one vote per person, recognizes A, B, C or the feature name, and sets unclear replies aside. Run it, print the totals and list the unclassified replies with a one-line reason for each.Write a short follow-up post within 500 characters that reports the aggregate result, says how many replies were counted and how many could not be classified, and states that the vote guides the decision rather than making it. Name no one who voted.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: Meta: Threads API, posts, 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.
codex mcp add tareno --url https://tareno.co/api/mcp
codex mcp login tareno
codex mcp get tarenolist_accountsChecked:
No. Tareno has no poll tool for Threads, so the vote is a post that asks for replies. That works because Tareno reads replies, and Codex can count them with a small script.
It keeps the first valid vote per account and ignores later ones. That is a rule you can state in the post. Accounts are not people, so treat the result as a signal and not as an election.
The script sets them aside and lists them with a reason. Read them yourself, because some are feature ideas you did not offer, and those can matter more than the votes.
Publish the aggregate and the number of replies you could not classify, and say that the result guides the decision. Do not name voters, and do not present a small count as the will of all users.
It can, but an unattended run should only read replies and print totals. Keep posting and scheduling out of it, so the follow-up always passes your approval in the dashboard.
No. A scheduling request is a pending action in Tareno, and Threads receives the post only after you approve it in the dashboard. `get_action_status` shows what happened afterwards.