< agent lab />

Inside the control room.

This is how I think about agentic AI. Every system I ship follows a similar shape: an orchestrator brain, a typed set of tools, a memory layer, and a channel for the user to talk to it.

< generic agent architecture />

How an agent thinks

USER INPUT
text · image · voice
→
orchestrator
AGENT BRAIN
OpenAI Agents SDK · Gemini
→
OUTPUT
WhatsApp · Streamlit · API
tool
Web Search

Live web retrieval via SERP APIs

Tavily · SerpAPI
tool
RAG Knowledge Base

Cited answers from documents

LangChain · Pinecone
tool
Code Execution

Sandboxed Python for analysis

Python REPL
tool
External API Call

Connect to any HTTP service

n8n · Fetch
tool
Human Escalation

Route to a human when uncertain

WhatsApp · Slack
< interactive demo />

Try it yourself

Pick a scenario and watch a representative execution trace step by step. These demos mirror the architecture patterns used in the shipped projects below.

Input
"What is the attention mechanism in transformers?"
○
Embedding Query
○
Vector Search
○
Reranking Results
○
Generating Answer
< recorded traces />

Agent runs you can reason about.

Live demos are risky for public agent systems, so this page uses safe recorded traces and representative runs. Each trace highlights the decision points a recruiter or client should inspect.

safe demo mode
< case studies />

Agents I've shipped

< tech ecosystem />

How the pieces connect

Channels
  • WhatsApp Business API
  • Streamlit
  • REST API
  • CLI
Orchestration
  • n8n
  • OpenAI Agents SDK
  • Custom Router
  • MCP / ACP
Models
  • Google Gemini (text + vision)
  • OpenAI GPT-4 / 5
  • HuggingFace OSS
  • Whisper (ASR)
Knowledge
  • LangChain
  • Pinecone
  • ChromaDB
  • Postgres pgvector
Tools
  • Web Search
  • Code Execution
  • File I/O
  • External APIs
Memory
  • Redis (short-term)
  • Postgres (long-term)
  • Conversation summarization