Use when building custom agent loops. Modify tool dispatch, history management, hooks, control flow.
npx skills add https://github.com/vercel-labs/seal --skill ai-python-custom-loop
Keep the default shape unless you must change control flow:
class MyAgent(ai.Agent):
async def loop(self, context: ai.Context):
while context.keep_running():
async with (
ai.stream(context=context) as stream,
ai.ToolRunner() as runner,
):
async for event in ai.util.merge(stream, runner.events()):
yield event
if isinstance(event, ai.events.ToolEnd):
runner.schedule(context.resolve(event.tool_call))
context.add(stream.message)
context.add(runner.get_tool_message())
Rules:
context.keep_running() at the top of each turn.ai.stream(context=context) so model, messages, tools, output type, and params stay together.Agent.run hides replay events from callers.ToolEnd, use context.resolve(event.tool_call). It handles validation, approval gates, and cached replay results.tool.fn directly unless you also handle validation, approvals, and cached results.ToolRunner.schedule(...).ToolRunner.schedule(...) also accepts a zero-arg async callable that returns ai.events.ToolCallResult.runner.add_result(ai.tool_result(...)).stream.message, then runner.get_tool_message(). context.add(...) skips replay messages.context.resolve(...) build the gated call. Use ai-python-serverless-execution for request boundaries.ai-python-durable-execution.Take vercel-labs/ai-python-custom-loop from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.