Agents

💡 This post is part of a series on Antigravity configuration:

• Where does Antigravity look for Agent Skills?
• Where does Antigravity look for MCP Servers?
• Where does Antigravity look for Rules and Workflows?
• Where does Antigravity look for Hooks?

In today’s post, I’ll talk about Hooks in Antigravity, what they are, how to configure them, and some shortcomings.

Hooks

Hooks allow you to run custom scripts or programs at specific points in the Antigravity agent lifecycle, such as before or after model or tool calls. They are a way to extend the functionality of the agent. Hooks run synchronously as part of the agent loop and they can be useful for things like adding context, validating actions, enforce policies or logging interactions.

💡 This post is part of a series on Antigravity configuration:

• Where does Antigravity look for Agent Skills?
• Where does Antigravity look for MCP Servers?
• Where does Antigravity look for Rules and Workflows?
• Where does Antigravity look for Hooks?

I’ve been exploring different ways of customizing Antigravity and where it saves its various configuration files. For Agent Skills, see Where does Antigravity look for Agent Skills? and for MCP Servers, see Where does Antigravity look for MCP Servers?.

💡 This post is part of a series on Antigravity configuration:

• Where does Antigravity look for Agent Skills?
• Where does Antigravity look for MCP Servers?
• Where does Antigravity look for Rules and Workflows?
• Where does Antigravity look for Hooks?

In my previous post, I explored where Antigravity (AGY) looks for agent skills. In this post, I’ll briefly explore the same for Model Context Protocol (MCP) servers and mention the MCP server caching that’s worth knowing about.

💡 This post is part of a series on Antigravity configuration:

• Where does Antigravity look for Agent Skills?
• Where does Antigravity look for MCP Servers?
• Where does Antigravity look for Rules and Workflows?
• Where does Antigravity look for Hooks?

Skills are an open standard for extending agent capabilities. A skill is a folder containing a SKILL.md file with instructions that the agent can follow when working on specific tasks.

In my Agent Protocols - MCP, A2A, A2UI, AG-UI post, I provided a high-level overview of some of the main agent protocols: MCP, A2A, A2UI, and AG-UI. In the Agent-User Interaction Protocol (AG-UI) with Agent Development Kit (ADK) post, I zoomed into the AG-UI protocol and showed how it can be used with Google’s Agent Development Kit (ADK).

In today’s post, I’ll zoom into the A2UI protocol and show how it can be used with Google’s Agent Development Kit (ADK).

In my previous post, I provided a high-level overview of some of the main agent protocols: MCP, A2A, A2UI, and AG-UI. In this post, I will zoom into the AG-UI protocol and show how it can be used with Google’s Agent Development Kit (ADK).

Recap: Agent-User Interaction Protocol (AG-UI)

AG-UI is an open, lightweight, event-based protocol, created by CopilotKit, that standardizes how agent backends connect to agent frontends.

It feels like every other month, there is a new agent protocol and it’s getting hard to keep track of which protocol is used when. Recently, I looked into some of the main agent protocols and in this post, I will provide a high-level overview of MCP, A2A, A2UI, and AG-UI.

TLDR

If you’re too busy or too impatient to read the whole blog post, here’s a summary of the protocols along with links to samples in my repository: