I gave Claude Code our entire codebase. Our customers noticed. | Al Chen (Galileo) episode artwork

EPISODE · Apr 6, 2026 · 45 MIN

I gave Claude Code our entire codebase. Our customers noticed. | Al Chen (Galileo)

from How I AI · host Claire Vo

Al Chen is a field engineer at Galileo, an observability platform for AI applications, where he works on the front lines with enterprise customers asking highly technical questions. Despite never having held an engineering role, Al has built a system using Claude Code to query Galileo’s 15 separate repositories, combine that with Confluence documentation and customer-specific quirks, and deliver hyper-personalized answers that would otherwise require constant engineering support.What you’ll learn:How to use Claude Code to query multiple repositories simultaneously for customer supportWhy code is often a better source of truth than documentationHow to combine repository context with Confluence and Slack using MCPsThe “customer quirks” system that creates hyper-personalized deployment guidesHow to build virtuous loops that turn single customer questions into scalable knowledgeWhy information organization matters less in the AI eraA simple 16-line script (written by Claude Code) that pulls the latest main branch across all your repositories to keep your context currentHow to reduce engineering interruptions to near-zero by empowering customer-facing teams to query the codebase directly—Brought to you by:Orkes—The enterprise platform for reliable applications and agentic workflowsTines—Start building intelligent workflows today—In this episode, we cover:(00:00) Introduction to Al Chen(02:50) The problem: documentation wasn’t enough(04:23) Pulling 15 repos into VS Code(06:03) How Claude Code queries the entire codebase(08:00) Why current code beats documentation(08:31) The pull script that keeps everything updated(09:54) Opening projects at the multi-repo level(11:40) Live demo: answering deployment questions(13:25) The customer quirks system(15:00) Living in chaos: why organization matters less now(17:03) Competing on customer experience, not just product(18:20) Should customers be able to query the code directly?(20:05) Where humans still add value(25:46) Using AI for reactive Slack support(29:16) The “and then” workflow discovery(32:07) Scaling processes across the team(34:07) Lightning round and final thoughts—Tools referenced:• Claude Code: https://claude.ai/code• VS Code: https://code.visualstudio.com/• Pylon: https://usepylon.com/• Confluence: https://www.atlassian.com/software/confluence—Other references:• Slack: https://slack.com/• Kubernetes: https://kubernetes.io/• Stack Overflow: https://stackoverflow.com/• Intercom: https://www.intercom.com/—Where to find Al Chen:LinkedIn: https://www.linkedin.com/in/thealchen/Company: https://www.rungalileo.io—Where to find Claire Vo:ChatPRD: https://www.chatprd.ai/Website: https://clairevo.com/LinkedIn: https://www.linkedin.com/in/clairevo/X: https://x.com/clairevo—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

Episode metadata supplied by the publisher feed · Published Apr 6, 2026

Embed this episode

Ready to play

I gave Claude Code our entire codebase. Our customers noticed. | Al Chen (Galileo)

0:00 45:47

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

No similar episodes found.

Frequently Asked Questions

How long is this episode of How I AI?

This episode is 45 minutes long.

When was this How I AI episode published?

This episode was published on April 6, 2026.

Can I download this How I AI episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.
URL copied to clipboard!