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

The key thing there is that we there's actually a lot of value in having like multi-turn um uh conversations from like the orchestrator or the assistant to like the sub agent.

Whereas like, you know, a tool call is basically just like one RPC.

And so oftentimes what will happen is um, you know, let's say

Let's say the the the user reaches out to their Rex assistant and says, Hey, like am I allowed like how much am I allowed to expense per person for dinner tonight?

I'm taking my team out.

Uh and the

the uh you know your assistant's gonna then reach out to the policy agent.

Maybe the policy agent needs to know in order to answer that question, maybe it needs to know like whether this was um uh was like a customer event, a team event, or whether you're traveling.

And so it may actually send instead of and it can't just answer the question.

So it's gonna reply back to the the assistant and say, hey, you I need you to ask uh this clarifying question.

And so then the assistant will return to the user ask clarifying questions.

question and then they'll basically have this sort of multi s multi-turn conversation across multiple agents versus it just being encapsulated in like a single uh call and response tool call.

And so there are still like all the all the sub agents have a ton of tools, but I I think of like the MCP and and tool usage as being like the interface to all of our conventional uh imperative systems and that not the the AI space.

chat back exactly exactly and that's the thing is like w okay and one of the ways that we actually grafted this into Nastro before we we built our own framework was to was to make every sub agent a tool uh and then the input was just natural language the output was natural language and the if you needed to have multi multi-turn um you would basically just put the full like

our conversation and as you kept calling calling the sub agent as a tool.

And it's just like at that point you're like, okay, the ergonomics are kind of the framework framework is fighting me on this.

It's actually helpful for us to basically conceive of it as an org chart and like it's the agent org chart with uh with um you know my EA is DMing other specialists uh and having brief conversations to support me as their client.

Yep.

into your spiel on it.

Yeah, of course.

Showing 181–200 of 667 · page 10 of 34