Loading...
Google Antigravity/TarenoAntigravity's agents leave a trail: notes, screenshots, a list of what they tried.
Google Antigravity / Tareno
Watch what happens right after you connect Tareno: your assistant can see your social accounts, and you can start writing.
Google AntigravityIllustrated demo · no live account
Open the MCP server list from the Agent window menu, view the raw configuration and add a Tareno entry using serverUrl, the documented field for remote servers; current docs also accept url. Authorize in the browser, reload the list and ask for your connected accounts. Tareno has not completed a client test with Antigravity.
Guides from Google and Appwrite place MCP management in the Agent window menu, with a raw view of the configuration behind it. Menu labels have moved between releases, so read them against the version you have installed.
Add a Tareno entry under mcpServers using the hosted address shown on the right. Current Antigravity docs specify serverUrl for remote servers and also accept url. If the server does not appear, check the server list and logs, then compare the entry with the docs for your installed version.
Accept the browser sign-in and reload the server list. Google's codelab reports that tokens are not shared between Antigravity surfaces such as the IDE and the command line, so each one may ask you again.
Ask Antigravity for your connected accounts before it drafts anything. Seeing the account you meant to post from is the confirmation that matters; an empty answer means the account still has to be connected inside Tareno.
{
"mcpServers": {
"tareno": {
"url": "https://tareno.co/api/mcp"
}
}
}Input
Provide the approved source and audience.
Review-ready drafts
Use Tareno and compare the returned draft IDs.
Approval in Tareno
Review text, media, account, and time in Tareno and approve.
Antigravity's strength is that agents work across the editor, a terminal and a browser, and write down what they did. That record is the raw material for three kinds of post, each with its own workflow page.
When an agent clicks through your web app on several screen sizes, the notes and screenshots show what was checked and what broke. Antigravity can turn the parts you export into a short post that names the defect, the fix and what the run did not cover, which reads as credible because it admits its limits.
Managing several agents teaches lessons about delegation, review and cost that other teams are asking about. Give Antigravity your notes from an Agent Manager session and it drafts a retrospective with what worked, what failed and what you would change, flagging every number it cannot source.
Bluesky is the one network where Tareno saves a whole thread as a single draft. A regression caught before customers saw it suits that format: what broke, how it was found and what changed afterwards, with screenshots placed on the posts that need them.
One guide for every network this agent can work with in Tareno, each with its own example, prompts and limits.
Cursor, GitHub Copilot and Junie also reach Tareno as MCP servers from an editor, with different configuration files. Antigravity's distinction is the Agent Manager and its browser agent, which produce notes and screenshots of what an agent actually did. If your content comes from agent runs rather than from commits, that record is what makes the posts concrete.
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:
Configure Tareno as a remote MCP server using the documented Antigravity setup. Start with a read-only list_accounts call and verify that the intended profiles are returned before creating drafts. The setup is documented; a completed Tareno client test is not yet recorded.
Current Antigravity docs specify serverUrl and explicitly note that url also works. Because details can differ by surface and release, compare your file with the current Remote MCP guide and check the server list for its connection state.
Google's codelab reports that OAuth tokens are not shared across Antigravity surfaces such as the IDE and the command line. Authorizing once per surface is expected and does not mean the first connection failed.
No. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches LinkedIn until you approve it in the dashboard. Antigravity can only report that the action is pending and read its status afterwards.
What was not covered. A post that names one defect found and one thing the run did not check is more believable than a list of passes, and it fits comfortably in the length limits of X and Bluesky.
Yes, as a draft. Bluesky is the one network where Tareno saves a root post and up to 24 replies of 300 characters each as a single draft. Antigravity can write the sequence and save it, and you approve the request.
Look at every image before you upload it to the Tareno library, and re-take any that shows a real address, order number or token. Antigravity cannot judge what is private, and Tareno only receives what you provide.
Usually `list_accounts` to confirm the destination, `list_media` to find the screenshots you uploaded and `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything.
Start with your Tareno account, connect your agent and prepare drafts. You approve what goes live.