Skip to main content
If you’d rather start from working code than write an agent from scratch, the idun-agent-template repository has nine runnable examples you can clone and adapt. Each template is a self-contained folder with its own config, dependencies, and agent code. Pick the one closest to what you’re building and modify from there.

​
LangGraph templates

​
ADK templates

​
Get started

1

Clone the template repo

2

Pick a template

3

Install dependencies and configure

4

Run it

Runs migrations, seeds the DB from the template’s config.yaml, opens the browser at http://localhost:<port>/ (default 8000; override with --port or IDUN_PORT), and serves the standalone app. idun init is idempotent, so you can re-run it on the same folder. For routine restarts that skip migration/seed work, prefer idun serve.

​
Which template should you pick?

  • First time with Idun? Start with langgraph-simple. It’s the shortest path to a running agent.
  • Need tool calling? Use langgraph-tool-node. It follows the recommended LangGraph pattern.
  • Want MCP tools from the platform AND local tools? Use langgraph-tool-local.
  • Building with Google ADK? Start with adk-tool.
  • Need typed input/output schemas? Look at langgraph-structured or adk-structured.
  • Building a multi-step workflow? The langgraph-editorial-loop shows a researcher/writer/reviewer pattern with conditional routing.

​
Templates vs. the quickstart

The quickstart walks you through the minimal steps to run an agent (a few lines of code). Templates give you more structure: proper project layout, config files, environment management, and patterns you’ll need as your agent grows. Both paths end at the same place: an agent running under the standalone with chat UI, admin, and traces.
Last modified on May 18, 2026