> ## Documentation Index
> Fetch the complete documentation index at: https://docs.idun-group.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent frameworks

> Connect LangGraph or Google ADK agents to Idun Engine and run them as production-ready services.

Idun Engine wraps your agent code into a FastAPI service through framework-specific adapters. You write your agent in the framework you prefer, and the engine handles streaming, checkpointing, guardrails, and observability through a unified API.

Each adapter implements a common `BaseAgent` protocol. Your clients talk to the same HTTP API regardless of the underlying framework.

## Supported frameworks

<Columns cols={3}>
  <Card title="LangGraph" icon="layers" href="/frameworks/langgraph">
    Graph-based agents with full AG-UI streaming, checkpointing (in-memory, SQLite, PostgreSQL), and CopilotKit support. Has the most complete feature coverage of the supported frameworks.
  </Card>

  <Card title="Google ADK" icon="google" href="/frameworks/adk">
    Google's Agent Development Kit for Gemini-powered agents. Supports session and memory services through in-memory, Vertex AI, or database backends.
  </Card>

  <Card title="Deep Agents" icon="boxes" href="/guides/deepagents-with-idun">
    LangChain's framework for agents that plan, write to a virtual filesystem, and spawn subagents. Runs as a regular LangGraph agent in Idun (no separate adapter, no glue code).
  </Card>
</Columns>

### Documentation and source code

| Framework   | Docs                                                                                                  | Repo                                                                             |
| ----------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| LangGraph   | [docs.langchain.com/oss/python/langgraph](https://docs.langchain.com/oss/python/langgraph)            | [github.com/langchain-ai/langgraph](https://github.com/langchain-ai/langgraph)   |
| Google ADK  | [google.github.io/adk-docs](https://google.github.io/adk-docs/)                                       | [github.com/google/adk-python](https://github.com/google/adk-python)             |
| Deep Agents | [docs.langchain.com/oss/python/deepagents](https://docs.langchain.com/oss/python/deepagents/overview) | [github.com/langchain-ai/deepagents](https://github.com/langchain-ai/deepagents) |

<Note>
  Haystack support was removed in 0.6.0. Existing Haystack agent configs need to be ported to LangGraph or ADK before upgrading.
</Note>

## Feature comparison

| Feature                | LangGraph                     | Google ADK                     |
| ---------------------- | ----------------------------- | ------------------------------ |
| AG-UI streaming        | Yes                           | Yes                            |
| Checkpointing / memory | In-memory, SQLite, PostgreSQL | In-memory, Vertex AI, Database |
| CopilotKit support     | Yes                           | No                             |
| Guardrails             | Yes                           | Yes                            |
| Observability          | Yes                           | Yes                            |
| MCP servers            | Yes                           | Yes                            |

## How adapters work

Under the hood, the engine loads your agent through the adapter specified in your configuration. This gives you:

* **Unified API**: All agents expose the same HTTP endpoints for invoke, streaming, and chat.
* **Shared platform features**: Observability, guardrails, MCP tools, and memory work the same way across frameworks.
* **Consistent deployment**: The same `idun serve` command runs any supported framework.

Select the framework by setting the `type` field in the `agent` section of your `config.yaml`:

```yaml theme={"theme":{"light":"github-light","dark":"github-dark"}}
agent:
  type: LANGGRAPH    # or ADK
  config:
    # framework-specific fields
```

The engine validates that the `config` shape matches the selected `type` at startup. The standalone admin panel at `/admin/agent/` exposes the same field with a dropdown when you want to switch frameworks without editing YAML.

## Next steps

<Card title="LangGraph integration guide" icon="layers" horizontal href="/frameworks/langgraph">
  Graph-based agents with full AG-UI streaming, checkpointing, and CopilotKit support.
</Card>

<Card title="Google ADK integration guide" icon="bot" horizontal href="/frameworks/adk">
  Google's Agent Development Kit for Gemini-powered agents with session and memory services.
</Card>

<Card title="Custom adapter" icon="plug" horizontal href="/frameworks/custom-adapter">
  Build your own adapter to bring a different agent framework into Idun Engine.
</Card>

<Card title="Configuration reference" icon="file-text" horizontal href="/configuration">
  Full schema for `config.yaml` including agent, guardrails, MCP, observability, and more.
</Card>