AbstractInitializes the plugin.
A unique identifier for this plugin instance.
Callback executed after an agent's primary logic has completed.
This callback can be used to inspect, log, or modify the agent's final result before it is returned.
The agent that has just run.
An optional Content object. If a value is returned, it will
replace the agent's original result. Returning undefined uses the
original, unmodified result.
Callback executed after a response is received from the model.
This is the ideal place to log model responses, collect metrics on token
usage, or perform post-processing on the raw LlmResponse.
The context for the current agent call.
An optional value. A non-undefined return may be used by the
framework to modify or replace the response. Returning undefined
allows the original response to be used.
Callback executed after an ADK runner run has completed.
This is the final callback in the ADK lifecycle, suitable for cleanup, final logging, or reporting tasks.
The context for the entire invocation.
undefined
Callback executed after a tool has been called.
This callback allows for inspecting, logging, or modifying the result returned by a tool.
The tool instance that has just been executed.
An optional dictionary. If a dictionary is returned, it will
replace the original result from the tool. This allows for
post-processing or altering tool outputs. Returning undefined uses
the original, unmodified result.
Callback executed before an agent's primary logic is invoked.
This callback can be used for logging, setup, or to short-circuit the agent's execution by returning a value.
The agent that is about to run.
An optional Content object. If a value is returned, it will
bypass the agent's callbacks and its execution, and return this value
directly. Returning undefined allows the agent to proceed normally.
Callback executed before a request is sent to the model.
This provides an opportunity to inspect, log, or modify the LlmRequest
object. It can also be used to implement caching by returning a cached
LlmResponse, which would skip the actual model call.
The context for the current agent call.
An optional value. The interpretation of a non-undefined
trigger an early exit and returns the response immediately. Returning
undefined allows the LLM request to proceed normally.
Callback executed before the ADK runner runs.
This is the first callback to be called in the lifecycle, ideal for global setup or initialization tasks.
The context for the entire invocation, containing session information, the root agent, etc.
An optional Event to be returned to the ADK. Returning a value
to halt execution of the runner and ends the runner with that event.
Return undefined to proceed normally.
Callback executed before a tool is called.
This callback is useful for logging tool usage, input validation, or modifying the arguments before they are passed to the tool.
The tool instance that is about to be executed.
An optional dictionary. If a dictionary is returned, it will stop
the tool execution and return this response immediately. Returning
undefined uses the original, unmodified arguments.
Callback executed after an event is yielded from runner.
This is the ideal place to make modification to the event before the event is handled by the underlying agent app.
The context for the entire invocation.
An optional value. A non-undefined return may be used by the
framework to modify or replace the response. Returning undefined
allows the original response to be used.
Callback executed when a model call encounters an error.
This callback provides an opportunity to handle model errors gracefully, potentially providing alternative responses or recovery mechanisms.
The context for the current agent call.
An optional LlmResponse. If an LlmResponse is returned, it will be
used instead of propagating the error. Returning undefined allows
the original error to be raised.
Callback executed when a tool call encounters an error.
This callback provides an opportunity to handle tool errors gracefully, potentially providing alternative responses or recovery mechanisms.
The tool instance that encountered an error.
An optional dictionary. If a dictionary is returned, it will be
used as the tool response instead of propagating the error. Returning
undefined allows the original error to be raised.
Callback executed when a user message is received before an invocation starts.
This callback helps logging and modifying the user message before the runner starts the invocation.
The context for the entire invocation.
An optional Content to be returned to the ADK. Returning a
value to replace the user message. Returning undefined to proceed
normally.
Base class for creating plugins.
Plugins provide a structured way to intercept and modify agent, tool, and LLM behaviors at critical execution points in a callback manner. While agent callbacks apply to a particular agent, plugins applies globally to all agents added in the runner. Plugins are best used for adding custom behaviors like logging, monitoring, caching, or modifying requests and responses at key stages.
A plugin can implement one or more methods of callbacks, but should not implement the same method of callback for multiple times.
Relation with Agent callbacks:
Execution Order Similar to Agent callbacks, Plugins are executed in the order they are registered. However, Plugin and Agent Callbacks are executed sequentially, with Plugins takes precedence over agent callbacks. When the callback in a plugin returns a value, it will short circuit all remaining plugins and agent callbacks, causing all remaining plugins and agent callbacks to be skipped.
Change Propagation Plugins and agent callbacks can both modify the value of the input parameters, including agent input, tool input, and LLM request/response, etc. They work in the exactly same way. The modifications will be visible and passed to the next callback in the chain. For example, if a plugin modifies the tool input with before_tool_callback, the modified tool input will be passed to the before_tool_callback of the next plugin, and further passed to the agent callbacks if not short circuited.
To use a plugin, implement the desired callback methods and pass an instance of your custom plugin class to the ADK Runner.
Example: A simple plugin that logs every tool call.