Bring your repo, trace, architecture diagram, or design question. Leave with concrete decisions, failure modes, and next implementation steps.
architecture, traces, repo
failure modes & bottlenecks
concrete architecture changes
decision memo & next steps
Work used by engineers at
Not ideal for general AI strategy, prompt-writing basics, or non-technical chatbot setup.
I built the kinds of systems I review.
2K+ star agent orchestration framework. Patterns for multi-agent coordination, tool invocation, tracing, state management, and reliable agent loops.
Creator of LionAGI and former AG2/AutoGen maintainer. I've built the orchestration frameworks, inference infrastructure, MCP tooling, and verification systems that these reviews draw from.
From debugging agent loops to architecting multi-agent orchestration to building MCP servers in Rust — the sessions are based on patterns from systems I have built and shipped.
96K LOC pure Rust inference engine. Batching, routing, scheduling, latency/cost tradeoffs, and systems-level performance on Apple Silicon.
Rust MCP server with multi-tenant architecture, hybrid retrieval (HNSW + BM25), OAuth 2.1. Published on crates.io.
Formal verification in Lean4. 26K+ lines, 0 sorry. Reasoning about correctness, invariants, and failure modes in agent systems.
These frameworks encode the patterns I apply in sessions. Adoption optional.
Technical advisory for teams building MCP servers, agent orchestration, inference pipelines, and Claude Code workflows.
One focused question
Review a design or decision
Live problem solving
Full system review with deliverables
All sessions prepaid via Calendly. Need ongoing advisory? Email for retainer options.
You bring the problem — I bring the patterns. We'll work through your specific challenge together, whether it's agent orchestration, MCP integration, or figuring out why your system isn't behaving as expected.
Multi-agent coordination, memory systems, capability scoping. The architecture that determines whether your agents compose or collapse.
Model routing, prompt structure, fine-tuning decisions. Where your token budget is going and whether it's going to the right place.
Rust and Python pipelines, embedding systems, vector search, MCP servers. The performance layer under your agent stack.
Build vs buy, team structure, prioritization. A second opinion grounded in having built the full stack myself.
Hooks, MCP servers, multi-agent workflows, CLAUDE.md design. Get your team shipping with Claude Code at the level I use it every day.
Send a brief description of what you're building and where you're stuck when you book. A diagram, repo link, or error log goes a long way. The more context I have beforehand, the deeper we go during the call.
Rust, Python, TypeScript. Agent orchestration (MCP, tool-use, multi-agent coordination), inference infrastructure, embedding/retrieval systems, formal verification. If you're building AI systems that need to work in production, we'll find common ground.
Yes. Everything discussed is confidential. I can sign an NDA before the session if your legal team requires it.
Yes — for teams building complex agent systems, I offer weekly retainers with code review, architecture check-ins, and async support. Book a 30-minute session first so we can scope it.
60-minute sessions include 30 days of async follow-up via email. For anything beyond that, book another session or ask about a retainer.
Bring your repo, diagram, or design question. Leave with concrete decisions and next steps.
Book an architecture review