Learn LangChain with Phoebe

Two tracks from agent-curious to agents that ship

A leader track that teaches you to think, question, and decide about AI agents without a line of code - and a builder track that grows one real assistant, DataDesk, from a 40-line loop to a multi-agent system with memory, approval gates, and an eval suite. LangChain 1.x + LangGraph, taught from the official docs and Academy curricula.

2tracks
16sessions
1running project
45min per session

The leader track 🀝 · for C-level, managers & curious minds · 6 x 45 min · no code, ever

Thinking mode: what agents are, how they fail, how to govern them, and how to make the build-buy-fund decisions - each session ends with questions to ask your data team.

The builder track πŸ› οΈ Β· for practitioners Β· 10 x 45 min Β· Claude API or local Ollama

One growing artifact: DataDesk, a data-team assistant. Every session upgrades the same code - and every capability is built by hand first, so the framework never gets to be magic.

🧭 Builder 1 · easy

Do you even need a framework?

Build an agent with no framework, rebuild it in three lines of LangChain 1.x, and learn the honest alternatives card.

β–Ά Builders start here
🧱 Builder 2 · easy

Models, messages, tools

init_chat_model, the Claude ↔ Ollama one-line swap, content blocks, and structured output DataDesk can validate.

DataDesk v0.2
πŸ€– Builder 3 Β· medium

create_agent, properly

Inside the 1.x harness: multi-tool agents, system prompts as constitutions, and streaming that feels alive.

DataDesk v1
πŸ§… Builder 4 Β· medium

Middleware: the production layer

PII scrubbing, summarization, retries, Claude-to-local fallback - and the yanked-release lesson in pinning versions.

DataDesk grows armor
πŸ•ΈοΈ Builder 5 Β· hands-on

The LangGraph mental model

State, nodes, edges, routers - the graph under everything, and when to eject from create_agent down to it.

DataDesk gets a spine
πŸ’Ύ Builder 6 Β· hands-on

State, memory, persistence

Checkpointers, thread identity, and the resurrection moment: kill the process, restart, and the conversation continues.

DataDesk v2
🚦 Builder 7 · hands-on

Human-in-the-loop and time travel

Approval gates before write-actions (approve, edit, reject) and rewinding a thread to fork a what-if.

Governance, in code
πŸ“š Builder 8 Β· medium

RAG the 1.x way

Retrieval as a tool the agent chooses to call: DataDesk reads the team wiki, cites its sources, and admits gaps.

DataDesk reads docs
πŸ‘₯ Builder 9 Β· hardest

Multi-agent and subgraphs

Supervisor, specialists, Send fan-out - plus the cascade experiment that shows exactly why checkers exist.

DataDesk hires an analyst
πŸŽ“ Builder 10 Β· hardest

LangSmith: trace, eval, ship

Tracing in two env vars, an eval suite with an LLM judge, shipping options - and DataDesk's graduation checklist.

DataDesk graduates
easy - everyone medium hands-on / deciding hardest

Choose your path πŸ—ΊοΈ

Two doors, one course. Leaders never see code; builders never sit through governance theory they have not felt in a demo first.

🀝 Leader (no code, ever) a1β†’ a2β†’ a3β†’ a4β†’ a5β†’ a6
πŸ› οΈ Builder (grow DataDesk) b1β†’ b2β†’ b3β†’ b4β†’ b5β†’ b6β†’ b7β†’ b8β†’ b9β†’ b10
🌱 Curious follower (a taste) a1β†’ a2β†’ b1
πŸš€ Full journey (lead AND build) a1-a6β†’ b1-b10

The knowledge map 🧠

Both tracks at a glance - hover a session to spotlight its concepts, click any node to jump in.