# Can Google Antigravity write up a UI regression it found as a Bluesky thread?

> Source: https://tareno.co/agents/antigravity/bluesky
> Language: en
> Last reviewed: 2026-10-24
> 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.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Google Antigravity (antigravity) |
| 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 | 2026-10-03 |
| 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: Google Antigravity · Network: Bluesky · Hub: [Google Antigravity and Tareno](https://tareno.co/agents/antigravity)

## Short answer

**Can Antigravity turn a regression report into a Bluesky thread and save it 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.

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.

## Example: a team writes up a checkout regression its browser agent caught

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.

## Step by step

1. **Open the MCP server list.** 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.
2. **Enter Tareno's address.** 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.
3. **Authorize, reload and read.** 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.
4. **Export notes and screenshots.** Pick the screenshots that show the problem and the fix, and remove real addresses or tokens before they enter the Tareno library.
5. **Write what happened, honestly.** 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.
6. **Save the thread and approve.** 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.

## Prompts to copy

### Summarize the finding

```text
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.
```

### Check the screenshots

```text
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 the thread

```text
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.
```

### Save the thread

```text
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.
```

## Bluesky in Tareno

- Tareno saves a Bluesky thread as one draft, so the story can run in order and each screenshot can sit on the post that explains it.
- Tareno's configuration for Bluesky allows up to four images per post with a limit of 2 MB each, which a cropped screenshot meets easily.
- Posts are limited to 300 characters, so a CSS fix has to be a single line of plain text, since the configuration has no code formatting.
- Tareno does not read posts or replies on Bluesky, so Antigravity cannot see whether other teams recognized the problem.

Official rules ([AT Protocol lexicons: app.bsky.feed.post and app.bsky.embed](https://github.com/bluesky-social/atproto/tree/main/packages/api/lexicons/app/bsky), checked 2026-10-25):

- Post text is limited to 300 graphemes and 3,000 bytes, so an emoji counts as one grapheme but can use several bytes.
- A post can embed up to 4 images, each up to 2,000,000 bytes.
- Video embeds accept MP4 up to 300,000,000 bytes, with up to 20 caption files in WebVTT. Tareno's configuration is stricter: one MP4 of up to 180 seconds and 100 MB.

## Mistakes to avoid

- Leaving real data in a screenshot. Check addresses, tokens and order numbers.
- Overclaiming impact. State that the agent found it in testing, if that is what happened.
- Assuming every remote URL field is supported. The docs specify serverUrl and accept url, but the legacy httpUrl field is not supported.
- Assuming one authorization covers everything. Surfaces keep their own tokens, per Google's codelab.

## What does not work

- Antigravity cannot judge whether a screenshot shows private data, so a person looks at every image before it is uploaded.
- It cannot read replies to the thread on Bluesky, because Tareno does not expose posts or replies for Bluesky.
- It cannot send anything to Bluesky on its own, because every time request stops at your approval in the dashboard.

## Frequently asked questions

### Can Antigravity create a Bluesky thread in Tareno?

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.

### Why might the server show no tools?

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.

### Is it fine to publish a bug we caught ourselves?

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.

### Do I authorize once for every Antigravity surface?

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.

### How is the fix shown without code formatting?

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.

### Can Antigravity send the thread to Bluesky itself?

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.

## Tareno tools used

- `list_accounts`
- `list_media`
- `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

- [Google Antigravity × Tareno overview](https://tareno.co/agents/antigravity)
- [Media library](https://tareno.co/features/media-library)
- [Approval workflows](https://tareno.co/features/approval-workflows)
- [Post scheduling](https://tareno.co/features/post-scheduling)
- [Remote MCP setup](https://tareno.co/docs/mcp)
