~/talk

HOW TO BUILD YOUR OWN AI AGENT: THE COMPLETE ARCHITECTURE FOR ENGINEERING TEAMS

slides:none on file

Architectural blueprint for a production agent that ties system context, tool descriptions, and just-in-time knowledge via an ingestion pipeline from git Notion Slack Jira into embeddings stored in a vector database, plus memory and multi-agent orchestration over MCP and REST. Execution uses an agentic loop where the LLM requests tools and the agent enforces guardrails or human approvals. Observability relies on OpenTelemetry tracing all inputs, outputs and tool calls. Cost control uses a cheap classifier to route requests and avoid bills reaching hundreds of thousands or millions per month.

AI-written summary · about

  1. 0:00Why build custom agents
  2. 3:20Core agent architecture
  3. 5:03System context design
  4. 6:26Tool integration strategies
  5. 8:55Semantic search for knowledge
  6. 12:48Orchestrating multiple agents
  7. 14:56Agent communication protocols
  8. 15:59Security and guardrails
  9. 17:44Observability challenges
  10. 20:12Cost control for AI agents
  11. 21:55Closing and next steps
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.