LEPA Support Agent
A LangGraph support workflow for LEPA: typed state, conditional routing, tools, memory, and a multi-agent split behind FastAPI.
- Python
- LangGraph
- FastAPI
- SQLite
- OpenRouter
A public repo of small AI engineering projects — terminal agents, MCP, LangGraph, and async document workflows — built while learning in public.
AI Learning Tracker is my public learning and project repo. Personal study logs stay private; the code is meant to be cloned. Phase 1 is TAM, DevAssist, and an agent harness. Later projects add a LangGraph LEPA support agent, a Temporal document pipeline, and an AI job application assistant with human review.
I wanted to move into AI/LLM engineering by shipping small, complete projects instead of notebook demos — and to keep the code public.
Each project teaches one idea: tool calling, MCP, a thin harness, then a LangGraph support agent, durable document orchestration, and a job-application workflow that stops for a human. The repo is the index; articles on Medium walk through what I learned.
A LangGraph support workflow for LEPA: typed state, conditional routing, tools, memory, and a multi-agent split behind FastAPI.
An async document pipeline: upload or webhook, Temporal extract/analyze/summarize, then Trigger.dev email — without blocking the request.
Parse a job and a CV, explain the match, draft materials, then stop for a human. The AI never applies.
From reflection and tool use to evals, planning, and multi-agent systems — the concepts that changed how I think about building AI applications.
Parse a job and a CV, explain the match, draft materials, then stop for a human. The AI never applies.
How I combined webhooks, Temporal workflows, AI summarization, async notifications, and email into one small system.
Jobs, events, durable workflows, and background tasks — the concepts I needed before building an AI document pipeline.
What Project 2 became — end to end — and what I would change next.
What HITL actually means — and why asking “which LEPA area?” is not the same thing.
Intake, knowledge, and support — why split the work, and how LangGraph keeps the specialists in order.
Checkpoints, thread IDs, and how a LangGraph support agent remembers a conversation across turns.
Why agents need tools, how search_knowledge works over Markdown docs, and how the knowledge node uses them.
Project setup, state, nodes, edges, and how a support request actually moves from START to END.
How I finally made sense of orchestration, state, memory, and multi-agent workflows — and why I decided to build a LEPA support agent next.
How I built TAM — a CLI assistant that lists files, searches code, runs shell commands, and talks to free models on OpenRouter.