← All speakers

Bio, Work & Ideas

Louis-François Bouchard

Conference affiliation: Towards AI · 2026

Louis-François Bouchard is the co-founder and chief technology officer of Towards AI and the creator of What’s AI, an educational platform for people building practical AI systems. He focuses on the engineering decisions that determine whether language-model applications remain accurate, affordable, and useful beyond an initial demonstration.

Bouchard developed his career in Montreal, studying engineering at École de technologie supérieure and pursuing doctoral research in artificial intelligence and computer vision at Mila and Polytechnique Montréal. He also worked in applied AI and led AI development at designstripe.

He launched the YouTube channel behind What’s AI in 2020, initially explaining research papers before expanding into language models, retrieval, and AI engineering. He co-founded Towards AI in 2022 and left doctoral research in 2024 to concentrate on education and company-building. His open-source guides range from machine learning for beginners to practical AI engineering and large language models.

With fellow Towards AI co-founder Louie Peters, he co-authored Building LLMs for Production, a 2024 guide to production language-model applications covering prompting, retrieval, evaluation, fine-tuning, agents, deployment, and optimization.

  • Autonomy should match the problem. Bouchard distinguishes direct prompting, retrieval, predetermined workflows, autonomous agents, and multi-agent systems according to the control, cost, and flexibility each task requires. For one marketing application, he replaced a proposed multi-agent architecture with a single agent and specialized tools, preserving shared context and reducing handoff errors. His research-and-writing workflow similarly separates exploratory research from tightly constrained writing and human editorial judgment.
  • Context engineering must account for prompt caching. Working on Towards AI’s open-source tutor, Bouchard challenged the assumption that shrinking conversation history automatically saves money. Summarization can destroy cached context, discard important details, and trigger repeated retrieval; retaining the complete conversation sometimes improves cost, latency, and recall simultaneously. His context-engineering analysis emphasizes evaluating retention, retrieval, and compaction against actual application behavior.
  • AI Research OS makes research memory reusable. With Paul Iusztin, Bouchard built a file-based research-memory system that organizes notes, videos, repositories, and other materials into Markdown files, indexes, and lightweight research wikis. Agents can recover relevant knowledge across projects without requiring a vector database for every personal workflow. The presentation’s 10,994-note collection belongs to Iusztin, not Bouchard.

Through Towards AI’s courses, enterprise training, and AI engineering mentorship, Bouchard teaches engineers to measure reliability, preserve human oversight, and choose the simplest architecture that meets production requirements.

Read the topics behind these talks

3 conference talks

Key ideas

Scroll to read ↓

Combine exploratory research, file-based handoffs, structured editorial feedback, and a calibrated judge to turn a human brief into technical content you can inspect and improve.

  • Why a fluent post still needs research and editing
    0:32 ↗
  • Choose how much autonomy the task needs
    6:09 ↗
  • Keep coupled decisions in one agent
    13:15 ↗
  • Treat context as a budget
    16:15 ↗
  • Research broadly enough, then hand off a focused artifact
    20:22 ↗
  • Start with a human guideline and reusable services
    28:26 ↗
  • Separate the reasoning harness from the MCP server
    34:41 ↗
  • Make each research call inspectable
    40:06 ↗
  • Turn a video into a durable research artifact
    44:35 ↗
  • Connect the server and test one capability
    49:15 ↗
  • Use skills to load the research procedure
    56:14 ↗
  • Inspect the searches as well as the final report
    1:07:26 ↗
  • Build the writer’s context deliberately
    1:10:57 ↗
  • Teach the voice with representative examples
    1:19:10 ↗
  • Review in a separate context and return actionable feedback
    1:21:37 ↗
  • Run locally, then decide how to distribute the capability
    1:28:13 ↗
  • Follow the work through threads and traces
    1:33:06 ↗
  • Build evaluation data from the real writer
    1:37:00 ↗
  • Calibrate the judge against expert labels
    1:42:12 ↗
  • Read perfect scores in the context of their dataset
    1:46:37 ↗
  • New traces expose what the small evaluation missed
    1:53:05 ↗
  • Run the complete path from guideline to post
    1:55:00 ↗

Key ideas

Scroll to read ↓

An AI tutor’s compaction experiments show how cached history, retrieval, and hardware limits change what belongs in the context window—and when removing it becomes necessary.

  • The instruction was there. Why did the agent ignore it?
    0:34 ↗
  • One window, several kinds of context
    5:14 ↗
  • Start with inexpensive compaction
    8:51 ↗
  • Keep the source outside the window
    11:55 ↗
  • A shorter prompt can cost more
    15:32 ↗
  • Choose what changes, then measure it
    18:55 ↗
  • One agent, middleware, and two tools
    21:56 ↗
  • Retrieve a few useful chunks from a large corpus
    24:43 ↗
  • Give browsing a bounded filesystem
    27:07 ↗
  • Turn an intuitive configuration into an observable system
    32:17 ↗
  • Test answers, retained facts, and whether the policy ran
    36:23 ↗
  • Full history beats the initial defaults
    42:25 ↗
  • Cheaper cached inference preserves the same advantage
    47:10 ↗
  • Long-context recall and service cost are different questions
    53:24 ↗
  • Caching cannot make an oversized input fit
    55:36 ↗
  • Combine semantic retrieval with keyword search
    58:31 ↗
  • Name the constraint before choosing compaction
    1:00:33 ↗

Key ideas

Scroll to read ↓

A file-based research system connects saved notes to current work, then preserves sources, summaries, and new questions in a project wiki that can keep growing.

  • Finding the research you already saved
    0:00 ↗
  • When persistent research earns its setup cost
    3:31 ↗
  • Move memory out of the conversation
    7:59 ↗
  • V1: turn a topic and golden links into a report
    12:48 ↗
  • V2: let the second brain supply the seeds
    15:42 ↗
  • V3: preserve sources and build a reference index
    18:28 ↗
  • Read progressively, from summaries to raw evidence
    21:23 ↗
  • Let project knowledge change while protecting personal notes
    24:07 ↗
  • Launch research from an article brief
    27:04 ↗
  • Study harness architecture directly from repositories
    31:58 ↗
  • Start with only a few links
    34:25 ↗
  • Return to the wiki with a new question
    35:48 ↗
  • The remaining work is maintaining trustworthy memory
    36:46 ↗

References