Loading...
×Use Grok Build with Tareno to read the commits between two tags, write an X release post within 280 characters that names its evidence and save it as a draft you approve in Tareno.
Yes, once Tareno is added as a remote MCP server. Grok Build reads the commits and changelog between two tags, writes a post within 280 characters, lists the commits behind each claim and saves a draft through Tareno. Tareno has not completed a client test with Grok Build, and a time request stays pending until you approve it.
Last reviewed 2026-10-25 · Markdown version for AI agents
Release announcements go wrong in a familiar way: the author writes them from memory an hour after the build, forgets the change that mattered and includes one that was reverted. A terminal agent has the better source. Grok Build can read the commits between two tags, the changelog and the diff itself, and write the post from what is there. This page follows the maintainer of a small command-line tool through one release. The agent cites the commits that support each sentence, the maintainer checks them, and Tareno saves the result as a draft that waits for a time. The connection follows xAI's documentation and Tareno has not completed a client test, so the first step is a read-only call.
Imagine a maintainer who has just tagged version 2.4. In the repository she asks Grok Build for the commits since 2.3 and the changelog entry. Grok Build proposes the post: faster startup, down from 400 to 90 milliseconds on her benchmark, and a new flag. It lists three commit hashes for the speed claim. She checks the benchmark commit, finds the numbers were measured on a laptop and asks for that to be stated. Grok Build confirms her X account with list_accounts and saves the approved text with create_drafts. She picks a time in the Tareno dashboard.
Add Tareno as a remote server as the Grok Build overview describes, then ask for list_accounts. Your X account in the answer is the check; an empty answer means X has to be connected inside Tareno first.
Name the previous and the new tag. Ask for the commits and changelog between them, and for the single change a user will notice most, with the commit hashes that support it.
Open the commits behind each claim, especially numbers. A benchmark from one machine is a fact about that machine, so the post should say where it was measured or leave it out.
Ask for a post of up to 280 characters with the version number, one change and a link to the release notes. A second change belongs in a post of its own, since Tareno saves single posts for X.
Grok Build checks the handle with list_accounts and stores the wording through create_drafts, returning a draft ID. At this point no time exists, so nothing can go out.
Name a day, a time and an IANA zone. schedule_posts turns that into a pending action, which you release in the dashboard, and get_action_status then reports the outcome.
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 account you would use for a release post on X, and say clearly if you cannot reach Tareno.List the commits between tag v2.3 and v2.4 and read the CHANGELOG entry for 2.4. Name the one change a user will notice most, give the commit hashes that support it and mark any number that was measured on a single machine. Do not write the post yet.Write an X post within 280 characters for version 2.4 that states that change, includes the version number and the link [release notes URL] and contains no hashtags. Under the post, list each claim with the commit hash that supports it.Use Tareno to confirm my X account [handle] and save the approved post as a 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 09:00] in [America/Los_Angeles]. 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: 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_accountsChecked:
No. Grok Bot is a different product with its own connector and its own guide. This page is about Grok Build, the terminal agent, and the steps here do not apply to Grok Bot or the other way round.
So that every claim can be checked in seconds. If the agent cannot name a commit for a sentence, that sentence is either invented or a summary of something you should look at yourself, and it should come out of the post before approval.
It can quote a short snippet, but code rarely survives 280 characters well. A link to the release notes or the commit is usually better, and you should read any snippet for paths, tokens or names that should not be public.
A `list_accounts` answer that shows your X handle, then one saved draft you can open in Tareno. xAI documents the setup, but Tareno has not run a full session through Grok Build, so those two results are your proof.
In ~/.grok/config.toml for your user, or in .grok/config.toml inside the repository for project servers, per xAI's guide. A server that needs your personal sign-in belongs in the user file, not the committed project one.
Only after you approve the pending request in the dashboard. Until then it is a draft that nobody outside your account can see, and `get_action_status` afterwards reports whether X took it or refused it.