James Reggio

speaker

667 appearances 1 recordings 1 series first heard Jan 2026 last heard 17 Jan

James Reggio’s voice in public audio — every appearance, attributed to the second.

Trend

recordings per month · last 12 months

Recordings per month over the last 12 months — 1 in all, peaking in Jan 2026 with 1.

Appearances

newest first · ▶ plays the moment

Latent Space: The AI Engineer Podcast · Brex’s AI Hail Mary — With CTO James Reggio · 17 Jan 2026 podcast

But what we were finding is that um the wide range of different product lines that exist on BREX made it difficult for one uh like agent to perform well, uh, being responsible from everything from like expense management to finding and booking travel to answering policy and procurement questions.

And so that's when we started breaking down the problem uh and into into a variety of sub agents that sit behind an orchestrator.

And obviously this isn't something that can be implemented using Langgraph or Master even has the notion of these as like network switches and data.

But what we found is that it was easier for us when it came to being able to build evals for the system.

Uh we we kind of just hit the eject button and built our own framework, which is one in which um we have agents that are able to uh to basically DM with other agents and have multi-turn

conversations amongst themselves to coordinate to um to complete a test to uh or like to complete an objective and um

What's what's been nice about that is it means that like you can have your BREX assistant.

There's like one single one single like point of contact uh between you as an employee and the BREX product.

And then behind your assistant, um, if the company has like expense management turn on, you have that.

If they have reimbursements, there's another agent for that.

If they're they have travel attached to the route agent for that, it actually also then facilitates like our conception here is that um it, you know, it's like

generally like software encapsulation patterns taking like sort of projected into the agent space.

It also makes it easier for us to have like the team that owns and understands travel like be the ones to go and iterate on that without needing to worry about like redressing the total system um or needing like one team to own every single possible um act action you could take as an employee.

And I'll say that like I'm still of the mindset that somebody will build a a great framework and we

They evolve ultimately migrate to it, but or it might be us that we ultimately open source this, right?

Like but um but for us, like this is uh this has worked out quite well in like lieu of like a couple other approaches that we we tried along the way that just didn't perform well, which was to you know, overload the l the the agent with a variety of tools or contextual like context switching where we try to say, Oh, this conversation looks like it's more about reimbursement, so let's like update the the prompt with more reimbursement.

reimbursement context, like that was that was another approach that we took that didn't perform as well as actually having a reimbursement agent that it would collaborate with.

What about MCPs as like sub agents?

Oh yeah.

That's another pattern.

Showing 161–180 of 667 · page 9 of 34