Self-Hosted AI Agent Orchestration: A Full Tour
Clone the repo, bring the stack up, install a model, then build, run, and trace an agent — the full tour.
Walkthrough · 9:34
Two ways to give an agent knowledge, with no code: upload a document, or crawl a website. The video creates a legal source from an uploaded PDF and a technical source by crawling the TheYgent docs (capped at 20 pages, with optional JavaScript rendering for sites that need a browser). Both are embedded by a local Nomic embedding model into pgvector in your own Postgres, and the crawl log shows which pages made it in.
Then it builds an agent on the canvas: an LLM with two retrieval tool nodes, each with a description that tells the model when to use it. In the test panel, a general question uses no tool, a question about data retention pulls section 4.3 of the PDF, and a question about importing a website searches the crawled docs — each tool call visible in the run trace. Publishing it makes the agent available over its endpoint.
The LLM in this demo is a hosted model; any model with tool calling, local or hosted, works the same way.
Clone the repo, bring the stack up, install a model, then build, run, and trace an agent — the full tour.
Speech-to-text, a model, and text-to-speech wired on the canvas — a spoken conversation with an agent you built.
A local model triages and handles the easy work; the hard question goes to a hosted API — one graph, each branch calling its own model.
Build the images, load them into a cluster, apply the manifests, and sign in — the same stack, on Kubernetes.