Working now
- Supervisor routing
- Streaming interface
- Agent-activity visualization
Chat
An earlier flight-search chat demo, kept for how it shows agents handing off work and calling tools in real time.
Why I built it
Agent demos frequently hide routing, tool use, intermediate state, and failure behind one response.
How it works
- Request
- Route
- Tool activity
- Visible response
A supervisor routes to bounded agents while the interface exposes streaming output and agent activity.
Where it stands today
A working demo was deployed in May 2025 and is offline now. Its reusable value is the pattern of making agent routing and tool use visible.
Not there yet
- Framework and data dependencies need a provenance audit.
How it got here
- Started as a FastAPI websocket chat with rate limiting
- Rebuilt around a LangGraph supervisor, streaming agent handoffs and tool calls live
- Next.js front end with sign-in and voice agents; demo deployed
What comes next
Next step
Produce a small synthetic reference with visible state.
Later ideas, not current features
- Extract the observable-agent pattern into a focused reference
What I checked, and what stays bounded
Dated evidence
- Working educational demo observeddeployment
Boundaries it keeps
- Not presented as a flight business
- Use mock or safely licensed data for public extraction
My role
Built the orchestration, streaming interface, voice experiments, and activity visualization.