Skip to main content
Packaged adapters are not built yet. This page describes what is planned. Everything below already works today by writing the glue yourself — see Bring Your Own Agent.
Silo’s agent contract is deliberately small: a function receiving task, tools and callTool. Any framework can be adapted to it in a few lines, and no adapter is required to use Silo. Planned packaged adapters:

What an adapter has to do

Only two things, whichever framework you are wrapping:
  1. Translate the tool schemas. Silo hands you { name, description, inputSchema } per tool, with inputSchema as JSON Schema. Most SDKs accept that shape directly or with a thin rename.
  2. Route tool calls through callTool. When the model asks for a tool, call Silo’s callTool rather than executing anything yourself, and feed the result back into the conversation.
That is the whole integration surface. There is no registration step, no runtime to host, and no lifecycle to implement.

Until they land

Write the loop yourself. Bring Your Own Agent documents the full contract, including how tool errors come back as values so a model can correct itself. If you build an adapter for a framework listed above, it is a welcome contribution.