Loading...
×Connect Google Antigravity to Tareno to turn a browser-agent regression report and its screenshots into a Bluesky thread: what broke, how it was found, what fixed it. Saved as one draft.
Yes, once Tareno is registered as an MCP server in Antigravity. It can take the notes and screenshots of a regression it found, write a thread of what broke, how it was found and what fixed it, and store the whole thread as one draft through Tareno. Published guides define the setup, and you approve in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
A regression story told well teaches more than a changelog: what broke, how it was found, why it had gone unnoticed. Teams that let an agent click through their web app sometimes catch one before a customer does, and the agent's notes and screenshots are the raw material. Bluesky suits the telling, because Tareno saves a thread there as one draft, with an image on the post that needs it. This page follows a small SaaS team through a short thread about a checkout button that stopped working on one screen size, with the connection steps published guides describe and with the care needed to keep customer data out of the screenshots.
Imagine a team whose Antigravity run on three screen sizes found that the checkout button was covered by a cookie banner at 360 pixels wide. The developer exports the run's notes and the two screenshots that show the problem and the fix. Antigravity writes a four-post thread: what broke, how the agent found it, the one-line CSS fix and what the team now tests. It finds the screenshots with list_media, checks that the notes do not claim the issue was seen by customers, and saves the thread with create_drafts. She removes a test email address from one image first.
Published guides place it in the Agent window menu under Manage MCP Servers, with a raw view of the configuration behind it. The labels differ by release, so read them against your installed version.
Add a Tareno entry under mcpServers pointing at the hosted endpoint. Current Antigravity docs specify serverUrl for remote servers and also accept url; the legacy httpUrl field is not supported. If the entry seems to do nothing, compare it with the docs for your Antigravity surface and version.
Accept the sign-in in the browser, refresh the list and ask for list_accounts. If your Bluesky account is returned the link works; if it is empty, connect the account inside Tareno and try again.
Pick the screenshots that show the problem and the fix, and remove real addresses or tokens before they enter the Tareno library.
Ask Antigravity for a thread that says what the agent saw and what it did not check. A regression caught in testing is a good story; claiming customers were affected is not, unless they were.
Antigravity finds the images with list_media and saves the thread through create_drafts as one draft. Give a time and an IANA time zone, and approve the request in the Tareno dashboard.
Read the exported notes from the browser-agent run and state what broke, at which screen width, how the agent found it and which fix was applied. Mark anything the notes do not support, such as customer impact, and tell me which screenshots show the problem and the fix.Use Tareno to look up the screenshots [checkout-360-before, checkout-360-after] in my media library. Tell me which one shows the problem, and list anything visible in either image that I should remove before it is public, such as email addresses or order numbers.Write a four-post Bluesky thread for Tareno: what broke, how the agent found it, the fix in one line and what we now test. Keep each post within 300 characters, do not claim customers were affected, and tell me which post carries which screenshot.Use Tareno to confirm my Bluesky account [handle] and save the approved thread as one draft with the screenshots on the posts you named. Return the draft ID, and request no time until I give you the day and the time zone.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: AT Protocol lexicons: app.bsky.feed.post and app.bsky.embed, read on 2026-10-25. 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:
Yes, as a draft: root post plus replies stored together. Registration as an MCP server comes first, following published guides, because no client test with Antigravity has been finished on Tareno's side.
A mis-named key in the raw configuration is the first suspect, since the guides warn that it can fail without an error. Check the entry against the Remote MCP setup page before anything else.
Yes, and readers like it. Say what the agent found and when, keep customer data out of the images and avoid claiming impact that did not happen. A short, specific thread builds trust.
Possibly each. Google's codelab reports that tokens do not carry across surfaces such as the IDE and the command line, so a repeated sign-in on another surface is normal.
As one line of plain text in a post, or in a screenshot with alt text that states the code. Tareno's configuration for Bluesky has no formatting, so avoid multi-line snippets.
No. Each time request is held in Tareno until you approve it in the dashboard, and from Antigravity you can only see that it is waiting. Nothing leaves for Bluesky before that approval.